bash-smart-approve:import

Import Existing Allow Rules

Convert Bash(...) permission rules from Claude Code settings into bash-smart-approve config.

Step 1 — Locate settings files

Read (in order of precedence, later overrides earlier):

1. ~/.claude/settings.json (user-global)
2. <cwd>/.claude/settings.json (project, committed)
3. <cwd>/.claude/settings.local.json (project, gitignored)

Also check ~/.claude/settings.local.json if it exists.

For each file, extract permissions.allow array. Ignore permissions.deny, permissions.ask, and non-Bash rules (e.g. Read(...), Edit(...), mcp__...).

Step 2 — Parse each Bash(...) rule

For every string matching Bash(<pattern>):

1. Strip the Bash( prefix and trailing ).
2. Normalize the pattern:
   • If it starts with $HOME/, $HOME\, ~/, or ~\ → strip that prefix.
   • If it starts with an absolute path like /Users/.../bin/X or /usr/bin/X → keep only the last segment (X).
   • Strip trailing .exe.
3. Identify the first token (the binary name):
   • Pattern git * → binary git
   • Pattern npm view:* → binary npm
   • Pattern aws-vault exec:* → binary aws-vault
   • Pattern bin/jira:* → binary jira
4. Classify:
   • shell interpreter (bash, sh, zsh, sudo, python, node -e, xargs, env, etc.) → skip with a warning to the user: "Rule Bash(bash:*) cannot be imported — shell interpreters are hard-denied for security."
   • curl or wget → also try to extract a domain from the pattern (regex: [a-zA-Z0-9*.-]+\.[a-zA-Z]{2,}). If a domain is found, add it to allowedCurlDomains. If no domain is extractable, skip with a note (too broad to auto-allow).
   • rm or rmdir → try to extract path arguments. If the pattern is too broad (rm * / rm -rf *), skip with a warning. If concrete paths are present (/tmp/jira*), add to allowedRmPaths.
   • anything else → add the binary to allowedBinaries.

Step 3 — Dedupe and propose diff

Merge against the existing bash-smart-approve config (don't re-add things already present).