[Feature]: Add ability to dynamically pause the queue when the agent turn / response asks a question #56
Description
What would you like to be added?
When the agent has finished processing a request and responded with output it can sometimes ask a question that requires human input. However, if you have an active queue it would just automatically consume the next item in the queue without giving the user a chance to response to the Agent's question. Therefore could there be a feature that would dynamically pause the queue during this situation to ensure that the flow of the conversation is smooth and we don't end up having to go back and forth between conversations while we now have to wait for that item in the queue to finish consuming before going back to the previous discussion? Maybe it is also worth using sounds to ping when the user's attention is required?
This actually reminds me of a similar issue when using the --print flag with Auggie CLI, where the agent might finish its response with a question but then the process is exited before the user has a chance to respond. However I guess in those cases they are meant to be used during automation tasks.
Why is this needed?
To ensure clarifying questions / discussions are smoothly addressed rather than simply continuing the queue (when it is in resume mode). This is especially an issue if you have a long list of items in the queue and you leave the agent running and before you know it you might have several agent turns that ended with a question that received no responses, and then you have to backtrack to those previous discussions to answer the agent, however in these cases there is a possibility the agent forgot what you were talking about - especially if the context window has been filled up by then.
Possible solution or alternatives
You have to watch the agent like a hawk, interrupt the agent in order to answer the question - at which point the next item from the queue might have already started being consumed, you answer the question, finish what you were doing, then you need to re-add the item you interrupted back into the queue and then resume the queue. Doing all of this can be cumbersome and breaks the flow and ease of use.
Additional context
No response