-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Delegation fixes #6165
Delegation fixes #6165
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
@openhands-agent Read the diff of this PR carefully. Understand what it tries to achieve. Then, we have two things to do:
Important: |
Hi! I started running the integration tests on your PR. You will receive a comment with the results shortly. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Hi! I started running the integration tests on your PR. You will receive a comment with the results shortly. |
Trigger by: Pull Request (integration-test label on PR #6165) Total cost: USD 0.00
Integration Tests Report (DeepSeek) Total cost: USD 0.00
Integration Tests Report Delegator (Haiku) Total cost: USD 0.00
Integration Tests Report Delegator (DeepSeek) Total cost: USD 0.00
Download testing outputs (includes both Haiku and DeepSeek results): Download |
Thanks! |
End-user friendly description of the problem this fixes or functionality that this introduces
Fix agent delegation; use events for communication between parent and delegates.
Fix the lockup when the model returns a message instead of a tool call.
Give a summary of what the PR does, explaining any non-trivial design decisions
Delegation was broken after we made the agent loop rely exclusively on a controller-as-observer logic. This PR proposes to fix it in a simple way: by forwarding to the delegate
should_step
on both MessageActions from 'user' and 'agent', except when waiting for user input is explicitly setshould_step
on DelegateAction too, it will create a MessageAction to kickstart the delegateAlso:
The code is ready for review - or this logic of delegation.
(please ignore the print() stuff, will clean up later)
Link of any specific issues this addresses
Fix #6162
To run this PR locally, use the following command: