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
[Bug] Subagent permissions not transitive via task tool — own bash permissions ignored #26747
Subagent permissions are not transitive when invoked via functions.task.
An agent with correct bash permissions cannot execute basic commands because it inherits the calling agent's restrictions instead of using its own.
Actual Behavior
The subagent cannot execute bash commands despite having correct permissions.
The global bash: deny rule from the main agent overrides the subagent's own permissions.
Expected Behavior
Each agent's own permission configuration should be respected. Subagents should not inherit the caller's restrictions.
Plugins
None
OpenCode version
1.14.46
Steps to reproduce
Configure an agent (e.g., developer-expert) with bash: allow permissions
Invoke it from a main agent via task tool
Ask it to run: New-Item -ItemType Directory -Path "test"
The command is blocked with: "The user has specified a rule which prevents you from using this specific tool call"
This was fixed in #27201 and should be out in the next release.
The fix keeps Plan Mode’s inherited edit restriction, but stops parent agent self-restrictions like read, bash, and task from erasing a subagent’s own explicit permissions.
Thanks for reporting this and linking it back to the permission inheritance regression.
Adding for visibility: #27201 fixed bash/read/task inheritance, but the edit permission gap remains. If your subagent has edit: allow and the parent has edit: deny, the edit tool still disappears. PR #27654 fixes this by checking the subagent's own permission declaration before inheriting the parent deny.
Activity
github-actions commentedon May 10, 2026
This issue might be a duplicate of existing issues. Please check:
Please review these before proceeding, and consider adding any new details to an existing issue if it covers the same root cause.
nabilfreeman commentedon May 11, 2026
Root cause is here #26700
ROKO108 commentedon May 12, 2026
Is the bug fixed in the latest release?
kitlangton commentedon May 13, 2026
This was fixed in #27201 and should be out in the next release.
The fix keeps Plan Mode’s inherited edit restriction, but stops parent agent self-restrictions like
read,bash, andtaskfrom erasing a subagent’s own explicit permissions.Thanks for reporting this and linking it back to the permission inheritance regression.
OrShmuel22 commentedon May 15, 2026
Adding for visibility: #27201 fixed bash/read/task inheritance, but the edit permission gap remains. If your subagent has
edit: allowand the parent hasedit: deny, the edit tool still disappears. PR #27654 fixes this by checking the subagent's own permission declaration before inheriting the parent deny.fix(task): subagent explicit edit:allow overrides parent edit:deny