You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
subagent reject (with reason) bugs out if multiple permission are stacked up #11932
the reject (with reason) for subagent permission checks works fine if subagent is asking for permission for a single tool call, but it bugs out and terminates the execution (of subagent) if there are multiple stacked permission prompts.
Plugins
NA
OpenCode version
1.1.49
Steps to reproduce
to simulate the issue:
make sure you have permissions set in the config or else general have all the access.
ask the main agent to use the general subagent to make some tool calls which all or atleast some requires permission.
reject any one with a reason.
the subagent session immediately terminates and main agent acknowledges that the subagent is not responding and sometimes it will run the tools itself or spawn another subagent session.
Both issues describe the same core problem: when multiple permission prompts are stacked, rejecting one causes the subagent session to terminate or get stuck. In #11490, the rejection submission gets stuck in the component, while in this issue, the session terminates entirely. They likely share the same root cause in the permission rejection handling logic.
Feel free to ignore if this doesn't match your specific case.
Activity
github-actions commentedon Feb 3, 2026
This issue might be a duplicate of existing issues. Please check:
Both issues describe the same core problem: when multiple permission prompts are stacked, rejecting one causes the subagent session to terminate or get stuck. In #11490, the rejection submission gets stuck in the component, while in this issue, the session terminates entirely. They likely share the same root cause in the permission rejection handling logic.
Feel free to ignore if this doesn't match your specific case.
github-actions commentedon Apr 5, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.