settings-local-json-wildcard-strategy-for-subagents
Subagents inherit parent session permissions from settings.local.json. Without broad wildcards covering Edit/Write for workspace paths and Bash for common CLI operations, every file modification by a subagent triggers a permission prompt that stalls the orchestrator. Replacing granular per-tool entries with workspace-scoped wildcards (e.g., Edit(/root/aj-workspace/**)) reduced entry count from 225 to 155 while expanding subagent capability — net improvement in both hygiene and functionality.
Related
- subagent-stall-root-cause-missing-edit-write-wildcards
- subagent-stall-root-causes-and-fixes
- subagent-permission-watchdog-hook-pattern
- clawteam-openclaw-multi-agent-swarm-evaluation
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- subagent-stalls-from-missing-edit-write-permissions
- wildcard-permissions-reduce-count-while-expanding-capability
- subagent-permission-stall-root-cause-and-fix
- settings-local-json-wildcards-supersede-specific-entries
- subagent-four-failure-modes-and-bulletproofing-fixes
- settings-local-json-225-to-155-via-wildcard-consolidation
- settings-local-json-missing-edit-write-wildcards
- subagent-edit-write-not-in-permissions-causes-stalls
- settings-local-json-wildcards-inherited-by-subagents-reduce
- settings-local-json-accumulates-one-off-permission-bloat-in
- one-off-session-permissions-accumulate-in-settings-local-jso
- fusion-invariants-lint-manual-no-drift-guard
- fusion-invariants-lint-manual-run-allows-drift