[Bug]: CLI stopped due to max iteration, instead of ask for whether to continue

[xingyaoww]

What problem or use case are you trying to solve?

CLI was directly interrupted when it hit 500 max iteration, instead of asking human to confirm whether to continue.

01:54:11 - openhands:WARNING: agent_controller.py:808 - Control flag limits hit
01:54:11 - openhands:ERROR: loop.py:24 - RuntimeError: Agent reached maximum iteration. Current iteration: 500, max iteration: 500
⚠️ Session was interrupted: error

Describe the UX or technical implementation you have in mind

When we hit max iteration, we should first ask human if they want to continue. If so, we should continue with the task

Additional context

If you find this feature request or enhancement useful, make sure to add a 👍 to the issue

[linear]

from joe:

Xingyao, what is the severity of this bug?

[enyst]

Well, in a sense it's not a bug, this hasn't been implemented for CLI.

Or, it's a usability bug.

The user can restart the session, using --conversation command line arg. Which requires the full session id that they need to track down manually in the session store.