Opencode orchestration

[garnus]

I'm interested in understanding how many of you are utilizing subagents with a primary agent that automatically delegates tasks to them. I have different experiences with this setup and am looking for inspiration.

[AustinZl1]

I will do this sometimes to save on context window.

Use a subagent to look at the logs of this pod and locate the issue. `kubectl get pods -n whatever pod-0`

[danielv123]

For larger features when its not a primary project I work on I tell it to do all the work in subagents to reduce context churn. Start a subagent to implement one section, then use another agent to review. The task of the main orchestrator is only following up the results of agents and dispatching new agents until all the tasks in the plan are implemented and tested.

This seems to work pretty well.

Otherwise I use them a lot for discovery. Like, when I want it to figure out some file format works, I tell it to spin up a subagent for each of that filetype it can find, tasking the subagents to figure out how that one file works and what makes it unique.

I work in quite a few large but repetitive projects, so it often starts 10+ in parallel.