𝗦𝘁𝗼𝗽 𝗖𝗹𝗶𝗰𝗸𝗶𝗻𝗴 𝗔𝗽𝗽𝗿𝗼𝘃𝗲: 𝗛𝗼𝘄 𝘁𝗼 𝗖𝘂𝘀𝘁𝗼𝗺𝗶𝘇𝗲 𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝗖𝗟𝗜 𝗣𝗲𝗿𝗺𝗶𝘀𝘀𝗶𝗼𝗻𝘀

I spent more time clicking "Approve" than reviewing work during my first task with Claude Code.

Every file read. Every git status. Every command.

By the end, I had clicked through forty prompts. I felt less trust in the changes than when I started. The permission system trained me to rubber-stamp everything without reading it.

You must configure permissions so you only approve what matters.

Claude Code is not a chat window. It reads files, writes files, and runs shell commands. A blanket "approve everything" approach is dangerous.

Modes define how Claude acts when no specific rule exists.

• default: Safe for new projects. Reads: Auto. Edits: Asks. Bash: Asks. • plan: Best for code reviews. Reads: Auto. Edits: Blocked. Bash: Blocked. • acceptEdits: Best for active coding. Reads: Auto. Edits: Auto. Bash: Asks. • bypassPermissions: Best for CI/CD. Reads: Auto. Edits: Auto. Bash: Auto.

You switch modes using the /permissions command.

Configuration follows a hierarchy. Higher scope always wins.

  1. Enterprise policy
  2. User settings (~/.claude/settings.json)
  3. Project settings (.claude/settings.json)
  4. Project local (.claude/settings.local.json)

Rules use a simple format: allow, deny, or ask.

Important: The evaluation order is deny, then ask, then allow. Deny always wins.

If you want to disable a tool entirely, use its bare name. If you want to restrict a tool, use a scoped rule with a glob pattern.

Example for active development:

  • Allow: Bash(npm run *), Bash(git status)
  • Deny: Bash(rm -rf *), Bash(curl *)
  • Ask: Bash(git push *)

You can also protect sensitive data. Use a deny rule for files like .env to ensure Claude never reads your credentials.

Pro tips for your workflow:

  • Use /permissions in the CLI to open an interactive UI.
  • Add rules for anything you approve more than twice.
  • Use flags like --permission-mode to set rules for a single session without changing files.
  • In CI/CD, use bypassPermissions with strict deny rules to keep your environment safe.

Stop rubber-stamping. Start configuring.

Source: https://dev.to/kapoormanish/stop-clicking-approve-how-to-customize-claude-code-cli-permissions-pnh

Optional learning community: https://t.me/GyaanSetuAi