permissionslisted

# Optimus Permissions Configure safe permission rules and a path-restriction hook so Claude Code agents can work autonomously inside the project without constant permission prompts, while blocking destructive operations outside the project. ## Security Model | Operation | Inside Project | Outside Project | |-----------|---------------|-----------------| | Read/Search | Allow | Allow | | Write/Edit | Allow | Ask user | | Write/Edit precious unversioned file | **Ask user** | Ask user | | Delete (rm/rmdir) | Allow | **BLOCKED** | | Delete precious unversioned file | **BLOCKED** | **BLOCKED** | | Git on feature branch | Allow | — | | Git on protected branch | **BLOCKED** | — | ## Step 1: Detect Existing Configuration 1. Check if `.claude/settings.json` exists. If so, read its full content — it will be preserved during merge. 2. Check if `.claude/hooks/restrict-paths.sh` (or `restrict-paths.*`) already exists. Note whether this is a fresh install or an update — report this to the user in Step 5. 3. Check if `.mcp.json` exists at the project root. If so, extract all MCP server names (top-level keys) for Step 4. Print a brief detection summary to the user: what exists, what will be created/updated. ## Step 2: Create Directory Structure ```bash mkdir -p .claude/hooks ``` ## Step 3: Install Path-Restriction Hook Copy the hook template to the project (overwrites any existing version): - Source: `$CLAUDE_PLUGIN_ROOT/skills/permissions/templates/hooks/restrict-paths.sh` - Desti