Claude Code has a permission system — and knowing how it works saves you from constant 'Allow?' prompts

Every time Claude tries to run a command, edit a file, or use a tool, it goes through a permission system. By default, it asks you to approve actions — which gets tedious fast.

The fix: configure allow rules in your settings. Add "Bash(npm run )" to auto-approve any npm script. Add "Read(~/.zshrc)" to let it read your shell config. You can also deny specific patterns: "Read(.env)" blocks Claude from ever reading your environment files.

Settings follow a hierarchy: Managed > CLI args > Local > Project > User. The most specific scope wins. Permission rules merge across scopes — they combine rather than override.

For teams, project-level settings live in .claude/settings.json (committed to git) for shared rules, and .claude/settings.local.json for your personal overrides.