/permissions rules

Build-along · ~10 min at your own keyboard

Approving the same safe command forty times trains you to stop reading prompts — which is how the one dangerous prompt slips through. /permissions sets standing rules: always allow these reads, always deny anything touching that folder.

The long version: Setting permission rules ↗

Mac: Mac: paths look like ~/Documents/contracts/**.

Windows: Windows: write paths with forward slashes in rules where possible, or match the exact style the prompt shows.

Do this

0/4

Checkpoints

▸You should now see your current rules listed after /permissions.
▸You should now see your allow rule skip the prompt on a safe command.
▸You should now see a denied path refuse even when you ask directly.

The three ways this goes wrong

The allow rule does not stop the prompts. — The pattern is too narrow or too different. Copy the exact command from the prompt and allow that pattern.
The deny rule does not block anything. — Check the path spelling and that the rule is saved in the project settings. Test again in a fresh session.
Allow rules are too broad and approve risky commands. — Remove any rule that allows all of one tool. Allow specific read-only patterns only.

Share what happened

Paste your added allow rule, your deny rule, and what happened when Claude hit the denied path.

Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].

🔒 Don't paste confidential, personal-health, or payment info.