Command
/permissions
Shows and lets you edit which tools and commands Claude is allowed to run automatically versus needing your approval for.
Claude Code asks before running things that could matter — installing packages, running arbitrary shell commands, editing files outside the project. /permissions is where those rules actually live: what's auto-approved, what always needs a prompt, and what's blocked outright.
Loosening permissions too far to avoid approval prompts trades safety for speed in a way that's easy to regret once something runs that shouldn't have. The better fix for prompt fatigue is usually scoping a specific, safe command (like your project's own test runner) to auto-approve, not disabling checks broadly.
Project-level permission rules also travel with the repo if committed, so a team can share the same guardrails rather than everyone tuning their own.
/permissionsFrequently asked questions
What does /permissions do in Claude Code?
Shows and lets you edit which tools and commands Claude is allowed to run automatically versus needing your approval for.
How do I use it?
Try: /permissions
Any caveats to know about?
Project-level permission rules also travel with the repo if committed, so a team can share the same guardrails rather than everyone tuning their own.
Is this covered in OG Flow Code Premium Toolkit?
Yes — /permissions and patterns like it are covered by the commands, and in higher tiers the specialist agents and guided skills, in OG Flow Code Premium Toolkit. Tiers start at $19.90.
Want the full command, hook, and template pack?
This is one pattern from the OG Flow Code toolkit. Choose the tier that fits your workflow, including Multi-Stack for six additional language stacks.
See pricing — from $19.90 once