-
Notifications
You must be signed in to change notification settings - Fork 7k
Add conversation start and stop endpoints #8883
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Looks like there are a few issues preventing this PR from being merged!
If you'd like me to help, just leave a comment, like
Feel free to include any additional details that might help me get this PR into a better state. You can manage your notification settings |
rbren
approved these changes
Jun 4, 2025
raymyers
pushed a commit
that referenced
this pull request
Jun 6, 2025
Co-authored-by: openhands <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
End-user friendly description of the problem this fixes or functionality this introduces.
Added new API endpoints that allow users to explicitly start and stop conversations. This gives users more control over conversation lifecycle management, enabling them to manually decide which conversations are running.
Summarize what the PR does, explaining any non-trivial design decisions.
This PR adds two new REST API endpoints to manage conversation lifecycle:
/api/conversations/{conversation_id}/start
- Starts a previously stopped conversation/api/conversations/{conversation_id}/stop
- Stops a running conversation without deleting itThe implementation leverages the existing conversation manager to handle the actual starting and stopping of agent loops. The endpoints include proper error handling and status reporting, returning appropriate HTTP status codes and messages.
Additionally, this PR includes fixes for nested runtimes to handle restarts more effectively and fixes for nested mount volumes, ensuring that conversations can be reliably started and stopped in containerized environments.
Link of any specific issues this addresses:
To run this PR locally, use the following command: