fix(review,work): omit mode parameter in subagent dispatch to respect user permissions (#522)

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Trevin Chow
2026-04-06 12:12:31 -07:00
committed by GitHub
parent 6f9069df7a
commit 949bdef909
10 changed files with 19 additions and 20 deletions

View File

@@ -144,6 +144,10 @@ Why: shell-heavy exploration causes avoidable permission prompts in sub-agent wo
When a skill orchestrates sub-agents that need codebase reference material, prefer passing file paths over file contents. The sub-agent reads only what it needs. Content-passing is fine for small, static material consumed in full (e.g., a JSON schema under ~50 lines).
### Sub-Agent Permission Mode
When dispatching sub-agents, **omit the `mode` parameter** on the Agent/Task tool call unless the skill explicitly needs a specific mode (e.g., `mode: "plan"` for plan-approval workflows). Passing `mode: "auto"` or any other value overrides the user's configured permission settings (e.g., `bypassPermissions` in their user-level config), which is never the intended behavior for routine subagent dispatch. Omitting `mode` lets the user's own `defaultMode` setting apply.
### Quick Validation Command
```bash