-
Notifications
You must be signed in to change notification settings - Fork 1.3k
The sub-task of Boomerang Mode has forgotten how to return to the parent task. #2499
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
In actual use, if the context of a subtask is too long, some mode instructions must be added to make the subtask remember to return to the parent task. |
To ensure that a subtask in Boomerang Mode remembers to return to the parent task when dealing with extremely long contexts, you need to explicitly signal task completion using the If you're experiencing issues where subtasks do not return to the parent task, it might be due to the To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
This had happened to me so I just have to manually tell it to return to the parent task. Sometimes I have to tell it a few times but it's worth it so it retains the completed context |
This is caused by the model not following instructions. This is an experimental model and this kind of inconsistent behaviour is an unfortunate reality. |
* Add Coverage Reporting * automate tests via github workflow * ensure documents are cleaned up at the end of the workflow * add changeset * backout github workflow changes * update changeset to reflect split --------- Co-authored-by: Dennis Bartlett <bartlett.dc.1@gmail.com>
App Version
v3.11.12
API Provider
OpenRouter
Model Used
gemini-2.5-pro-exp-03-25
Actual vs. Expected Behavior
Expected Behavior:
When a subtask is completed, it should remember to return to the parent task.
Actual:
When faced with an extremely long context, a subtask may forget to return to the parent task and instead switch to other modes or indicate the end of the task.
Detailed Steps to Reproduce
Relevant API Request Output
Additional Context
No response
The text was updated successfully, but these errors were encountered: