Repository navigation
Replies: 1 comment
|
Yes, you can use both in one session, and from the source they shouldn't fight: on OpenCode v2, where 1. Compatibility. 2. Orchestration. Goal Mode only acts when the session is about to go idle with nothing pending (llm.ts#L175-L185), and it returns without judging while any subagent the orchestrator launched is still running (goal.ts#L148-L153). A finished lane wakes the orchestrator through the host's normal subagent notice, and the check runs again after that turn. So it won't cut in while lanes or an Oracle gate are running. Where it adds something is when the orchestrator stops between passes with nothing running. 3. Completion. The reviewer is a separate call on the session's model. It judges your 4. Order. 5. Loops. With one driver I don't see a path to duplicate continuations. The friction is in the stopping rules: the reviewer is told "When in doubt, answer continue" (judge.txt#L18), while Deepwork treats leftover known issues as expected and caps gate re-reviews (SKILL.md#L26-L30, #L86-L88). So Goal may keep pushing after Deepwork writes its tombstone, and it will push past any per-pass check-ins you ask for. That is bounded by 50 rounds, three stalled rounds in a row, and a pause after 30 minutes with nothing running (goal.ts#L15-L19, #L184-L187). Each reviewer call also sends the full session context (generate.ts#L37-L64), which adds up over a long Deepwork run. |
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone!
Can I activate native Goal Mode and use Deepwork at the same time within a single OpenCode session?
For example, would this workflow be supported?
/goal <objective>./deepwork <task>to have the Orchestrator execute the task using Deepwork's phased workflow.A few things I'd particularly like to understand:
/goalfirst and then/deepwork, use them in the opposite order, or avoid combining them?Has anyone tried this combination? I'd especially appreciate feedback from the maintainer or anyone who has tested both features together.
Thanks!
All reactions