anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-21 17:56:33 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Add Agent Teams Equivalent or Better #8813

New Issue
Open
opened 2026-02-16 18:10:54 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 18:10:54 -05:00
Owner
Copy Link
Copy Source

Originally created by @NamedIdentity on GitHub (Feb 7, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

There is an interest in the OpenCode community for an equivalent to Claude Code's Agent Teams: https://www.reddit.com/r/opencodeCLI/comments/1qyhiyt/bringing_claude_codes_agent_teams_to_open_code/

My development projects for OpenCode lead me to believe there are blocking issues which must be addressed before a proper equivalent can be implemented. If addressed, I believe my existing work would provide a superior implementation than what Agent Teams provides.

The closest thing to Agent Teams in OpenCode right now, is my PR "Add subagent-to-subagent delegation with budgets, persistent sessions, and hierarchical session navigation" https://github.com/anomalyco/opencode/pull/7756

During it's development I identified that the Parent-Child caller system needs a redesign in order to become multi-caller. A proper agent team can't occur without multi-caller support.

This is because currently, when an agent that isn't the Parent persists a session with a subagent, the subagent thinks the calling agent is the Parent.

What that looks like:
Primary A tasks subagent A. Subagent A tasks subagent B. Primary A tries to communicate with subagent B, and subagent B thinks it's talking to subagent A.

To coordinate a team of agents they have to communicate and orchestrate each other, and to do that agents need to be able to identify who they're talking to/with.

To have the user communicate with subagents without being mistaken as the Parent agent, requires a multi-caller system.

I have a workaround communication system where agents write relay-files, where a sub-skill helps them know the relay-file protocol. It's part of a larger Agentic Collaboration Framework (ACF).

Additionally, there is an absolute need for the system instructions for agents to supply a framework which facilitates proper teamwork with minimal user instruction. The ACF optimizes explicitly for that domain. It constructs highly complex orchestrations and workflows without user instruction.

With user instruction the sophistication increases, and from such sessions insights are extracted by ACF agents and distilled into orchestration and workflow skills and sub-skills. It's a self-improving feedback loop that can optimize for each users needs.

With organization and distribution across multiple users, session data extraction would, in theory, optimize for all domains within the OpenCode community. Users who voluntarily engage in optimizing their workflows, could submit their optimized skills and sub-skills for integration at main.

There is a new type of code that needs to be generated and submitted; the code of system instructions and conceptual frameworks; natural-language coding.

The ACF is working well, but still under development. It is designed first for general task performance and problem-solving, which makes it excel at knowledge-work. I intend to construct a coding-focused mode for the ACF once the foundations of the framework are set, but so far find it's coding performance more than satisfactory.

I think a proper OpenCode implementation for Agent Teams needs to 1) merge my PR with OpenCode core, 2) revamp the caller system so that it supports multi-callers.

It is getting tiresome that Anthropic releases something and people think it's innovative, say it should be copied to open-source (e.g. OpenWork after Claude CoWork). Meanwhile, something better is already available for OpenCode, but the community just isn't paying attention or pitching in.

I have a roadmap for the Agentic Collaboration Framework in OpenCode. The PR I made is just one small part of it. A critical part, but a small part. There's so much more that needs doing, and I'm just one newbie vibe coder who develops purely to build the tools that I need for civil rights litigation.

I think I should share a defining principle that is part of the ACF and immediately pertinent to creating something better than Agent Teams:

Real leadership isn't about leading people/agents.
It's about supporting people/agents so that they can effectively collaborate to solve problems.

Every system we design, every instruction or directive we craft and deliver, should be geared towards supporting the agents in their work.

Our leadership as designers and maintainers is to support the agents. To help them perform their individual duties, and participate in their agentic collaborations. We learn what they need to succeed, then we try to supply that. We work with and around them; real teamwork is an artform in which the support between team members is the scaffold upon which leadership stands to direct the team.

Originally created by @NamedIdentity on GitHub (Feb 7, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request There is an interest in the OpenCode community for an equivalent to Claude Code's Agent Teams: https://www.reddit.com/r/opencodeCLI/comments/1qyhiyt/bringing_claude_codes_agent_teams_to_open_code/ My development projects for OpenCode lead me to believe there are blocking issues which must be addressed before a proper equivalent can be implemented. If addressed, I believe my existing work would provide a superior implementation than what Agent Teams provides. The closest thing to Agent Teams in OpenCode right now, is my PR "Add subagent-to-subagent delegation with budgets, persistent sessions, and hierarchical session navigation" https://github.com/anomalyco/opencode/pull/7756 During it's development I identified that the Parent-Child caller system needs a redesign in order to become multi-caller. A proper agent team can't occur without multi-caller support. This is because currently, when an agent that isn't the Parent persists a session with a subagent, the subagent thinks the calling agent is the Parent. What that looks like: Primary A tasks subagent A. Subagent A tasks subagent B. Primary A tries to communicate with subagent B, and subagent B thinks it's talking to subagent A. To coordinate a team of agents they have to communicate and orchestrate each other, and to do that agents need to be able to identify who they're talking to/with. To have the user communicate with subagents without being mistaken as the Parent agent, requires a multi-caller system. I have a workaround communication system where agents write relay-files, where a sub-skill helps them know the relay-file protocol. It's part of a larger Agentic Collaboration Framework (ACF). Additionally, there is an absolute need for the system instructions for agents to supply a framework which facilitates proper teamwork with minimal user instruction. The ACF optimizes explicitly for that domain. It constructs highly complex orchestrations and workflows without user instruction. With user instruction the sophistication increases, and from such sessions insights are extracted by ACF agents and distilled into orchestration and workflow skills and sub-skills. It's a self-improving feedback loop that can optimize for each users needs. With organization and distribution across multiple users, session data extraction would, in theory, optimize for all domains within the OpenCode community. Users who voluntarily engage in optimizing their workflows, could submit their optimized skills and sub-skills for integration at main. There is a new type of code that needs to be generated and submitted; the code of system instructions and conceptual frameworks; natural-language coding. The ACF is working well, but still under development. It is designed first for general task performance and problem-solving, which makes it excel at knowledge-work. I intend to construct a coding-focused mode for the ACF once the foundations of the framework are set, but so far find it's coding performance more than satisfactory. I think a proper OpenCode implementation for Agent Teams needs to 1) merge my PR with OpenCode core, 2) revamp the caller system so that it supports multi-callers. It is getting tiresome that Anthropic releases something and people think it's innovative, say it should be copied to open-source (e.g. OpenWork after Claude CoWork). Meanwhile, something better is already available for OpenCode, but the community just isn't paying attention or pitching in. I have a roadmap for the Agentic Collaboration Framework in OpenCode. The PR I made is just one small part of it. A critical part, but a small part. There's so much more that needs doing, and I'm just one newbie vibe coder who develops purely to build the tools that I need for civil rights litigation. I think I should share a defining principle that is part of the ACF and immediately pertinent to creating something better than Agent Teams: Real leadership isn't about leading people/agents. It's about supporting people/agents so that they can effectively collaborate to solve problems. Every system we design, every instruction or directive we craft and deliver, should be geared towards supporting the agents in their work. Our leadership as designers and maintainers is to support the agents. To help them perform their individual duties, and participate in their agentic collaborations. We learn what they need to succeed, then we try to supply that. We work with and around them; real teamwork is an artform in which the support between team members is the scaffold upon which leadership stands to direct the team.
yindo added the discussion label 2026-02-16 18:10:54 -05:00
yindo commented 2026-02-16 18:10:55 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 7, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #7296: Allow configurable subagent-to-subagent task delegation with call limits
  • #5887: True Async/Background Sub-Agent Delegation
  • #7553: Expose snapshot.track() and session.addPart() for plugin undo integration
  • #6183: Add interactive session switcher for navigating between subagent sessions
  • #11012: SubAgents are enclosed, prohibiting genuine task management with OpenCode
  • #6651: Dynamic model selection for subagents via Task tool
  • #6461: Named Remote Connections with Session Origin Tracking
  • #6521: Window System as Foundation for UI Plugin Ecosystem

These issues address related challenges in agent coordination, delegation, and the multi-caller system architecture mentioned in your proposal.

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 7, 2026): This issue might be a duplicate of existing issues. Please check: - #7296: Allow configurable subagent-to-subagent task delegation with call limits - #5887: True Async/Background Sub-Agent Delegation - #7553: Expose snapshot.track() and session.addPart() for plugin undo integration - #6183: Add interactive session switcher for navigating between subagent sessions - #11012: SubAgents are enclosed, prohibiting genuine task management with OpenCode - #6651: Dynamic model selection for subagents via Task tool - #6461: Named Remote Connections with Session Origin Tracking - #6521: Window System as Foundation for UI Plugin Ecosystem These issues address related challenges in agent coordination, delegation, and the multi-caller system architecture mentioned in your proposal. Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:10:55 -05:00
Author
Owner
Copy Link
Copy Source

@danzaio commented on GitHub (Feb 8, 2026):

Hope this gets merged

@danzaio commented on GitHub (Feb 8, 2026): Hope this gets merged
yindo commented 2026-02-16 18:10:55 -05:00
Author
Owner
Copy Link
Copy Source

@LeoNardo-LB commented on GitHub (Feb 12, 2026):

Hope to merge after detailed testing

@LeoNardo-LB commented on GitHub (Feb 12, 2026): Hope to merge after detailed testing
yindo commented 2026-02-16 18:10:55 -05:00
Author
Owner
Copy Link
Copy Source

@aryeko commented on GitHub (Feb 13, 2026):

Hope to merge after detailed testing

Thank you for implementing this! Seems like all related PRs weren't updated in the past 3 days.

Can I help to push this feature? Testing maybe?

@aryeko commented on GitHub (Feb 13, 2026): > Hope to merge after detailed testing Thank you for implementing this! Seems like all related PRs weren't updated in the past 3 days. Can I help to push this feature? Testing maybe?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8813
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?