[Bug] Subagent permissions not transitive via task tool — own bash permissions ignored

[ROKO108]

Description

Description

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

1. Configure an agent (e.g., developer-expert) with bash: allow permissions
2. Invoke it from a main agent via task tool
3. Ask it to run: New-Item -ItemType Directory -Path "test"
4. The command is blocked with: "The user has specified a rule which prevents you from using this specific tool call"

Operating System

Windows 10

Terminal

CMD

[github-actions]

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

• Subagent parent deny inheritance over-constrains delegated agents with explicit permissions #26700: Subagent parent deny inheritance over-constrains delegated agents with explicit permissions (nearly identical — parent agent's deny rules blocking subagents that have their own explicit allow permissions)
• Task tool permission override no longer works for nested sub-agents #8114: Task tool permission override no longer works for nested sub-agents (same symptom via task tool)
• [Security Bug] Subagent permissions not enforced - configured restrictions ignored #7474: Subagent permissions not enforced — configured restrictions ignored

Please review these before proceeding, and consider adding any new details to an existing issue if it covers the same root cause.

[nabilfreeman]

Root cause is here #26700

[ROKO108]

Is the bug fixed in the latest release?

[kitlangton]

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.

[OrShmuel22]

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.