-
Notifications
You must be signed in to change notification settings - Fork 39
Feature Request: Cancel job on user request in interactive mode #360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is a good idea. I've noticed that as well. I started on that, I will finish it early this week. |
/mycoder, can you have a look at this feature request? I thought that maybe an attempt was made to enable this via Ctrl-M or Cmd-M (on MacOS), but it doesn't seem to work. I think the goal would be to just stop processing on the main agent and allow the user to enter in new instructions, and then have it resume. The main agent should be able to communicate with its sub-agents using existing mechanisms to switch their priorities or to get them to stop (can the main agent force a stop in a sub-agent? If not we should add that? Like if a sub-agent was doing a research task, we can just get it to immediate halt and return.) |
I've implemented the feature to cancel a job in interactive mode. This implementation adds:
The PR is available at: #367 When using interactive mode, you can now:
The implementation clears the conversation history when a cancellation is requested, ensuring the agent stops the current task and focuses entirely on the new instructions. |
In the interactive mode, I would like to cancel execution when it's going south and enter new instructions.
The text was updated successfully, but these errors were encountered: