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

SubAgents are enclosed, prohibiting genuine task management with OpenCode. #7857

New Issue
Open
opened 2026-02-16 18:08:29 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:08:29 -05:00
Owner
Copy Link
Copy Source

Originally created by @davidbernat on GitHub (Jan 28, 2026).

Originally assigned to: @thdxr on GitHub.

Description

Hey OpenCode, there is very little documentation on your SubAgent strategy, and very little discourse happening.

Here is the issue:
Agent ==> creates SubAgent to do thorough research via Task ==> SubAgent sends summary back to Agent

SubAgents perform operations in their own context as their strength, but also as de-facto Task management.
This leads to the excruciating circumstance where the SubAgent "cannot be reentered" to continue operation.

For instance:

  • the SubAgent creates excellent in depth research but returns only a summary ==> SubAgent session is closed ==> Agent cannot instruct SubAgent to write its previous full research to a file, or improve, or further orchestrate.

You can imagine dozens of pretty obvious workflows which are hamstrung by this artificial limitation.
I understand that you have constructed this as a feature-not-a-bug but I am struggling to see its value.
It seems only a matter of time until workflows are written into prompts with specialty syntax anyway, like "@".

Prompt: Create a %Workflow[Research, Review, Bibliography such that Research uses @subagent/Researcher to etc. and so forth while Review takes the results from Research to cross-investigate using the etc. etc. and so on.

In the meantime I am manually deleting tool responses from the manually exported subagent session in question?
I am stating a critique of the order of priorities on this issue.

OpenCode v1.1.39.
Thanks.

Originally created by @davidbernat on GitHub (Jan 28, 2026). Originally assigned to: @thdxr on GitHub. ### Description Hey OpenCode, there is very little documentation on your SubAgent strategy, and very little discourse happening. Here is the issue: Agent ==> creates SubAgent to do thorough research via Task ==> SubAgent sends summary back to Agent SubAgents perform operations in their own context as their strength, but also as de-facto Task management. This leads to the excruciating circumstance where the SubAgent "cannot be reentered" to continue operation. For instance: - the SubAgent creates excellent in depth research but returns only a summary ==> SubAgent session is closed ==> Agent cannot instruct SubAgent to write its previous full research to a file, or improve, or further orchestrate. You can imagine dozens of pretty obvious workflows which are hamstrung by this artificial limitation. I understand that you have constructed this as a feature-not-a-bug but I am struggling to see its value. It seems only a matter of time until workflows are written into prompts with specialty syntax anyway, like "@". Prompt: Create a %Workflow[Research, Review, Bibliography such that Research uses @subagent/Researcher to etc. and so forth while Review takes the results from Research to cross-investigate using the etc. etc. and so on. In the meantime I am manually deleting tool responses from the manually exported subagent session in question? I am stating a critique of the order of priorities on this issue. OpenCode v1.1.39. Thanks.
yindo added the bugdocs labels 2026-02-16 18:08:29 -05:00
yindo commented 2026-02-16 18:08:29 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 28, 2026):

This issue relates to several existing issues about SubAgent design limitations. Please check these related issues:

  • #6584: [FEATURE]: Agent-level resume for subagents (resumeSessionId parameter)
  • #6491: Session does not automatically return to parent after subagent execution
  • #6907: Can't chat with the subagent session anymore
  • #10374: [FEATURE]: Allow 'aborted' agents to be continued
  • #2378: [Improvement] The ability to guide subagents on the right path
  • #6792: Task Tool Timeouts & Early Termination in Multi-Agent Conductor Pattern
  • #5887: [feat] True Async/Background Sub-Agent Delegation
  • #7296: [FEATURE]: Allow configurable subagent-to-subagent task delegation with call limits
  • #9280: [FEATURE]: Allow subagents to spawn subagents
  • #10802: TUI: Parent session appears stuck 'loading' when subagent is blocked
  • #4422: Primary agent responds in subagent view; delegated subagent views become inaccessible
  • #2906: Limit Subagent Tree Depth
  • #3023: Integrate Agent2Agent (A2A) Protocol for Enhanced Inter-Agent Communication
  • #6299: feat: Add /subagents command to view subagent tree

These issues all share the core theme of SubAgent enclosure and architectural limitations in task management workflows. The most directly related is #6584 which proposes a resumeSessionId parameter to continue subagent work across phases.

@github-actions[bot] commented on GitHub (Jan 28, 2026): This issue relates to several existing issues about SubAgent design limitations. Please check these related issues: - #6584: [FEATURE]: Agent-level resume for subagents (resumeSessionId parameter) - #6491: Session does not automatically return to parent after subagent execution - #6907: Can't chat with the subagent session anymore - #10374: [FEATURE]: Allow 'aborted' agents to be continued - #2378: [Improvement] The ability to guide subagents on the right path - #6792: Task Tool Timeouts & Early Termination in Multi-Agent Conductor Pattern - #5887: [feat] True Async/Background Sub-Agent Delegation - #7296: [FEATURE]: Allow configurable subagent-to-subagent task delegation with call limits - #9280: [FEATURE]: Allow subagents to spawn subagents - #10802: TUI: Parent session appears stuck 'loading' when subagent is blocked - #4422: Primary agent responds in subagent view; delegated subagent views become inaccessible - #2906: Limit Subagent Tree Depth - #3023: Integrate Agent2Agent (A2A) Protocol for Enhanced Inter-Agent Communication - #6299: feat: Add /subagents command to view subagent tree These issues all share the core theme of SubAgent enclosure and architectural limitations in task management workflows. The most directly related is #6584 which proposes a resumeSessionId parameter to continue subagent work across phases.
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 bug docs
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#7857
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?