#permissions

6 hacks

1.
Enable Bash sandboxing to auto-allow contained commands (code.claude.com)
Turn on `/sandbox` so OS-level filesystem and network boundaries replace many per-command Bash prompts.
0 points·13 hours ago·Terminal / Productivity / Cost Optimization·medium·discuss
2.
Prefer auto mode over --dangerously-skip-permissions (claude.com)
Enable auto mode so a classifier approves safe tool calls and blocks destructive ones — fewer prompts without a full permission bypass.
0 points·13 hours ago·Terminal / Productivity / Cost Optimization·easy·discuss
3.
Play a sound when Claude needs attention via Notification hooks (code.claude.com)
Add a Notification hook that plays a short sound when Claude is idle or waiting on permission so you can multitask without staring at the terminal.
0 points·13 hours ago·Terminal / Productivity / Cost Optimization·easy·discuss
4.
Block dangerous Bash with a PreToolUse hook (code.claude.com)
Add a deterministic PreToolUse hook that rejects destructive shell patterns before Claude can run them.
0 points·13 hours ago·Testing / Debugging·hard·discuss
5.
Commit shared .claude/settings.json for team permissions (docs.anthropic.com)
Check in project settings so every teammate gets the same allow/deny rules, hooks, and env defaults without redoing /permissions.
0 points·13 hours ago·Claude Code / CLAUDE.md·intermediate·discuss
6.
Allowlist safe Bash commands to stop approval fatigue (code.claude.com)
Use /permissions to allowlist read-only and trusted commands so you stop mindlessly clicking Approve.
0 points·13 hours ago·Terminal / Productivity / Cost Optimization·medium·discuss