Repository navigation
ACP subagents are invisible and can hang forever on permission prompts #32388
Description
Description
When OpenCode is used through ACP (opencode acp), Task subagents are not fully surfaced to ACP clients. The parent Task card is visible, but the child subagent stream, child tool calls, and child permission prompts are not reliably forwarded to the ACP client. If the child subagent asks for permission, the task can hang because the ACP client never receives a request to answer.
This is related to #21802, but from the ACP client side the problem also includes missing permission routing and missing real-time inspection of the child task. ACP clients should not need to read OpenCode private DB or internal event storage to support Task/subagent UX.
Expected behavior: child session metadata should be exposed while the parent Task is still running, child stream/tool activity should be visible in real time, and child permission prompts should be routed to the connected ACP client.
Plugins
No response
OpenCode version
1.16.2
Steps to reproduce
- Start OpenCode in ACP mode.
- Connect with an ACP client.
- Ask the agent to start a Task/subagent that runs a command needing approval, for example
ps aux. - Observe the parent Task tool call from the ACP client.
- If the child subagent requests permission, observe that the ACP client may never receive the permission prompt and the turn can hang.
Screenshot and/or share link
Related issues and PRs: #21802 #12133 #14592 #30635 #30639 #12136 #14588 #21801 #25165
Operating System
macOS 15.2
Terminal
TeamClaw ACP client integration
Activity
[-]ACP: Task/subagent child sessions are not fully visible or approvable from ACP clients[/-][+]ACP subagents are invisible and can hang forever on permission prompts[/+]github-actions commentedon Jun 15, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:), or Question.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Jun 15, 2026
Thanks for updating the issue! It now meets the contributing guidelines — clear description, reproduction steps, system info, and actual/expected behavior are all present. The needs:compliance label has been removed.
github-actions commentedon Aug 26, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.