feat: bulk permission pre-registration for frequently used tools in Claude Code

[JeremyDev87]

Purpose

During interactive sessions, Claude Code frequently asks "Do you want to proceed?" for repetitive tool uses (Bash commands, file edits, etc.). Users who trust the agent should be able to pre-register permissions for frequently used patterns to eliminate confirmation prompts.

Background

In the 2026-03-22 session, the conductor was interrupted 5+ times by permission prompts for:

• Bash commands: git, gh, tmux, yarn, node
• File edits: .claude/rules/, .claude/skills/, packages/rules/.ai-rules/
• MCP tool calls: codingbuddy tools

Changes

• .claude/settings.json or .claude/settings.local.json — Add permission allowlist entries
• Document recommended permission presets for common workflows

Proposed Permission Presets

Preset: "parallel-execution" (for taskMaestro conductor)

{
  "permissions": {
    "allow": [
      "Bash(git *)",
      "Bash(gh *)",
      "Bash(tmux *)",
      "Bash(yarn *)",
      "Bash(cat *)",
      "Bash(ls *)",
      "Bash(mkdir *)",
      "Bash(sleep *)",
      "Edit(.claude/**)",
      "Edit(packages/rules/.ai-rules/**)",
      "Edit(apps/mcp-server/**)",
      "Edit(docs/**)",
      "mcp__codingbuddy__*"
    ]
  }
}

Preset: "development" (general development)

{
  "permissions": {
    "allow": [
      "Bash(git *)",
      "Bash(yarn *)",
      "Bash(npm *)",
      "Bash(node *)",
      "Bash(npx *)",
      "Edit(src/**)",
      "Edit(tests/**)",
      "Edit(packages/**)"
    ]
  }
}

Implementation Approach

1. Audit current session's permission requests (from hooks/logs)
2. Group into semantic categories (git, build, edit, mcp)
3. Create preset configurations in .claude/settings.local.json
4. Document in .claude/rules/ for team sharing
5. Optionally: add /taskmaestro setup-permissions subcommand that applies the parallel-execution preset

Acceptance Criteria

• Permission presets documented for parallel-execution and development workflows
• .claude/settings.local.json updated with recommended allowlist
• Zero "Do you want to proceed?" prompts for covered patterns
• Presets are opt-in (not auto-applied)
• Security: exclude destructive commands (rm -rf, git push --force) from presets
• Can be merged independently

References

• Claude Code permissions docs: settings.json allow/deny patterns
• Incident: 2026-03-22 session — 5+ permission interruptions during parallel execution
• Parent: Improve taskMaestro parallel execution reliability (retrospective action items) #866