anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-23 02:36:57 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

subagent reject (with reason) bugs out if multiple permission are stacked up #8414

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

Originally created by @IdrisGit on GitHub (Feb 3, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

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:

  1. make sure you have permissions set in the config or else general have all the access.
  2. ask the main agent to use the general subagent to make some tool calls which all or atleast some requires permission.
  3. reject any one with a reason.
  4. 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.

Screenshot and/or share link

screen recording of the bug

https://github.com/user-attachments/assets/bd0668c1-0006-452a-a5ce-a9ad38944473

recorded sessions share link: https://opncd.ai/share/GjKq5gFf

Operating System

Omarchy

Terminal

Ghostty

Originally created by @IdrisGit on GitHub (Feb 3, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description 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: 1. make sure you have permissions set in the config or else general have all the access. 2. ask the main agent to use the general subagent to make some tool calls which all or atleast some requires permission. 3. reject any one with a reason. 4. 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. ### Screenshot and/or share link **screen recording of the bug** https://github.com/user-attachments/assets/bd0668c1-0006-452a-a5ce-a9ad38944473 recorded sessions share link: https://opncd.ai/share/GjKq5gFf ### Operating System Omarchy ### Terminal Ghostty
yindo added the bug label 2026-02-16 18:09:55 -05:00
yindo commented 2026-02-16 18:09:55 -05:00
Author
Owner
Copy Link
Copy Source

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

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

  • #11490: Submitting a subagent rejection doesn't handle stage properly

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[bot] commented on GitHub (Feb 3, 2026): This issue might be a duplicate of existing issues. Please check: - #11490: Submitting a subagent rejection doesn't handle stage properly 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.
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
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#8414
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?