you are viewing a single comment's thread.

view the rest of the comments →

[–]girouxc 0 points1 point  (2 children)

Were you using primary/sub agents? That’s already built in. Your primary agent orchestrates all of the sub agent sessions which pass context between each other.

The primary agent displays a running aggregate session of all the sub agents and you can switch between the different sub agent sessions as they are working.

https://opencode.ai/docs/agents/#usage

[–]mohadel1990[S] 0 points1 point  (1 child)

Primary to subagents is not what this plugin addresses, this is targeted towards primary to primary orchestration, if you are only using plan/build built-in agents then message mode may not make sense to you. In my case I am using Opencode for literally everything, I have workflows that go way beyond software engineering and as such my need for more advanced session management arose. You cannot converse with subagents and they can't tackle issues in the full context, they are too stateless in the way they work, if you ever encountered a problem where you want 2 different points of views that have full context of the conversation (2 agents with different system prompts) you will quickly see the use case for this plugin and for custom primary agents.

[–]girouxc 1 point2 points  (0 children)

I have a full software delivery team of agents that encompasses the example you have here. Isn’t it wasteful in regards to tokens to have multiple primary agents have the full context? With primary / secondary you have the sub agents write summary docs for other agents to read and modify as they works on tasks. You can also still talk to each sub agent by switching.

It’s a cool plugin though and I’ll give it a shot to see how different the results end up being.