Zak Siddiqui
opened 2 days ago
-
Name Previous Value Current Value Assignee
robin
wh
-
Name Previous Value Current Value Assignee
wh
empty -
Name Previous Value Current Value Assignee
empty wh
-
-
-
Name Previous Value Current Value Assignee
wh
empty -
Name Previous Value Current Value Assignee
empty wh
-
-
Name Previous Value Current Value Assignee
wh
empty -
Name Previous Value Current Value Assignee
empty wh
-
Name Previous Value Current Value Assignee
wh
empty -
-
Name Previous Value Current Value Assignee
empty wh
-
-
Name Previous Value Current Value Assignee
wh
empty -
Name Previous Value Current Value Assignee
empty wh
-
-
Name Previous Value Current Value Assignee
wh
empty -
Name Previous Value Current Value Assignee
empty wh
-
Added a TASK_PROMPT rule so agents wait for any started sub-agents to finish before ending the run. That should stop OpenCode from exiting early (and printing the success marker) while Oh My OpenCode sub-agents are still in flight.
See pr #82.
-
State changed as build OD-7687 (16.0.8) is successful
-
OneDev
changed state to 'Closed' 2 days ago
Previous Value Current Value Open
Closed
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Watchers (3)
The AI workspace prompt TASK_PROMPT does not respect sub-agents in open code, particularly when using Oh My OpenCode.
I have a custom open code agent which uses Oh My Open Code.
Most of the time it works perfectly fine; however, I would say one in five times it fails because it creates sub-agents, and when it does so, it often returns
__ONEDEV_RUN_PROMPT_SUCCESS__after initiating the subagents but before the subagents respond.Therefore, there needs to be, as part of the prompt, some kind of instruction that tells OpenCode to wait for sub-agents to complete.