Summary
Add Python development tool permissions to ~/.claude/settings.json for parity with Rust tooling.
Current State
Global settings include Rust/Cargo permissions:
"Bash(cargo check:*)",
"Bash(cargo build:*)",
"Bash(cargo test:*)",
"Bash(cargo clippy:*)",
"Bash(cargo fmt:*)",
"Bash(cargo run:*)",
"Bash(cargo doc:*)",
"Bash(cargo add:*)"
But no Python equivalents, causing permission prompts during Python development.
Proposed Changes
Add to ~/.claude/settings.json:
"Bash(ruff format:*)",
"Bash(ruff check:*)",
"Bash(pytest:*)",
"Bash(pip install:*)",
"Bash(pip3 install:*)"
Context
This came up during claude-event-bus development where running make check (which calls ruff and pytest) required permission prompts each time.
Alternatives
- Project-specific
.claude/settings.json - but these are common tools used across many Python projects
- Just
Bash(make:*) - already allowed, but doesn't cover direct tool invocation
Decision
Summary
Add Python development tool permissions to
~/.claude/settings.jsonfor parity with Rust tooling.Current State
Global settings include Rust/Cargo permissions:
But no Python equivalents, causing permission prompts during Python development.
Proposed Changes
Add to
~/.claude/settings.json:Context
This came up during claude-event-bus development where running
make check(which calls ruff and pytest) required permission prompts each time.Alternatives
.claude/settings.json- but these are common tools used across many Python projectsBash(make:*)- already allowed, but doesn't cover direct tool invocationDecision