Introduce a "Pause button" to the Cascade Workflow, to allow for context updates and direction fixes when the Agent is clearly not going in a direction that it should be.
Raymond Johnson
There are many times when the Thinking process will reveal what the agent is intending to do, then the output shows that it just arbitrarily made a decision about something that is critical to application flow design. If we had a Pause button, where we could highlight the reasoning of the Agent, and provide specific direction, the process could be more efficient, and less work would need to be done to repair the broad implications a single change can make in a codebase. I know we can just press stop, but that dumps the workflow the agent is doing creating a completely new execution path.
Jayant Mathoera
This would be a great feature!
a
andromedacgb@gmail.com
I totally agree with you... or if the agent asks me I'm in the right direction.
Guy G
This, 100 times this! Or allow us to limit how many iterations it goes through before pausing. And/or allow us to position prompts in its "path" so that it reads the prompt after the next iteration completes.