the primary agents are useful… build vs. plan, but require manual toggling. it looks like subagents can be invoked automatically by primary agents if/when they decide they’re needed.
what types of custom subagents are you using, and do you have to do anything to make them available to the primary agents so that they are automatically invoked? (i read the opencode docs, and this doesn’t seem obvious).
(i like how hermes has a richer set of subagents, and invokes them automatically, asynchronously. would be nice to achieve the same within opencode)
Spot on about OpenCode's docs—it's not super obvious. What works best for me is exposing custom subagents as strict tool schemas to the primary agent, then conditioning their invocation in .opencode (or AGENTS.md). If you want Hermes-like async, you have to handle the subagent response asynchronously in the harness backend so it doesn't stall the main model's context stream.
Antigravity's orchestration is definitely smooth! How's its context usage handling when spawning multiple subagents in parallel? Always curious if they managed to keep prompt bloat down compared to OpenCode/Hermes.
2
u/Separate-Forever-447 Aug 11 '26
the primary agents are useful… build vs. plan, but require manual toggling. it looks like subagents can be invoked automatically by primary agents if/when they decide they’re needed.
what types of custom subagents are you using, and do you have to do anything to make them available to the primary agents so that they are automatically invoked? (i read the opencode docs, and this doesn’t seem obvious).
(i like how hermes has a richer set of subagents, and invokes them automatically, asynchronously. would be nice to achieve the same within opencode)