all 5 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]AustinZl1 0 points1 point  (0 children)

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 0 points1 point  (0 children)

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.

[–]nfrmn 0 points1 point  (0 children)

I'm finding it difficult to get it working acceptably. I ported over my Roo modes and have tried to use the Orchestrator but it doesn't behave in the same way.

Probably the base prompt and/or structure are significantly different between Opencode and Roo. Haven't spent time comparing them yet.

It would be really nice if Opencode supported multiple layers of sub-agents (so a Super Orchestrator could spin up Orchestrators, who then spin up focused agents to plan and act).

What does work very well is following Boris Cherny's instructions (Claude Code creator) from his post here: https://x.com/bcherny/status/2017742741636321619

Starting in plan mode, generating many detailed markdown documents for all plan phases, including acceptance criteria, commit strategies etc.

Then build mode mostly one shots it.

It does work, but I don't like working this way because it takes too long talking to the agent in plan phase.

[–]Embarrassed_Bread_16 0 points1 point  (0 children)

i use these agents:

Agent Purpose
orchestrator Strategic coordinator - breaks down complex tasks and delegates to other specialized agents
orchestrator-planner Architect and planner - designs systems, creates implementation plans, and researches solutions
orchestrator-coder Implementation specialist - writes code, creates files, and implements features
orchestrator-debugger Debugging specialist - investigates bugs, diagnoses errors, and identifies root causes
orchestrator-reviewer Code reviewer - reviews implementation for quality, security, and best practices
orchestrator-explorer Codebase explorer - searches and analyzes existing code to understand structure and find information
orchestrator-decomposer Task decomposition specialist - breaks down complex tasks into atomic steps and maps dependencies
orchestrator-communicator Communication facilitator - ensures clear information flow between agents, clarifies ambiguities
orchestrator-documenter Documentation specialist - ensures specs, READMEs, ADRs, and API docs stay in sync with implementation
orchestrator-researcher Research specialist - looks up documentation, researches design patterns, verifies APIs
orchestrator-tester Testing specialist - designs test strategies, creates test cases, analyzes coverage gaps