permission-tuner — Claude Code command: analyze access rules
permission-tuner analyzes why Claude Code keeps prompting for permissions or denying operations, then generates rules to reduce confirmation fatigue.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat permission-tuner does
permission-tuner reads your ~/.claude/settings.json config and session transcripts, counts denials by category, and identifies three classes of friction: ask rules that trigger even in auto mode, hook blocks on harmless commands, and classifiers that wrongly reject routine tasks.
The command preserves dangerous rules—they stay in deny or ask to protect your project. After analysis, it presents recommended changes you can apply by hand.
Run /permission-tuner with no arguments to start. Results show which autoMode.environment or autoMode.allow entries will stop unnecessary prompts, and which hooks produce false positives.
What it helps with
- remove ask rules that force Claude Code out of auto mode
- fix hook false positives blocking safe operations
- add autoMode entries for a classifier that wrongly rejects routine work
- cut down permission confirmation requests
Example prompts for the agent
- /permission-tuner
- Run permission-tuner to find out why Claude Code keeps asking for permissions
- Apply permission-tuner recommendations to your autoMode config
How to install permission-tuner
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflow2Manually: put the files in place
.claude/commands/permission-tuner.mdCall it with /permission-tuner. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/permission-tuner.mdCall it with /prompts:permission-tuner. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/permission-tuner.prompt.mdManually: put the files in place
.gemini/commands/permission-tuner.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about permission-tuner
How do I install permission-tuner in Claude Code?
Run /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow. The command loads from .claude/commands/permission-tuner.md.
What does permission-tuner do?
It reads your permission rules and recent denials, finds what triggers the prompts, and suggests rule changes to reduce them.
What's an ask rule and why does it block auto mode?
An ask rule requests confirmation even when auto mode is on. permission-tuner suggests dropping the ones you always approve, because they freeze automation.
Source text
permission-tuner.md · MIT
--- description: Analyze permission prompts and auto mode denials, then generate permission rules and autoMode entries that reduce prompt fatigue --- # /permission-tuner - Permission Optimization Find out why Claude Code keeps prompting or denying, and fix the cause. ## Quick Start Run this command to: 1. Read your permission rules and `autoMode` config 2. Count denials by kind from recent session transcripts 3. Separate hook false positives, classifier blocks, and ask-rule prompts 4. Present recommended changes for your approval ## What It Does - **Ask rules you always approve**: suggests removing them, since ask rules prompt even in auto mode - **Classifier blocks on routine work**: suggests `autoMode.environment` or `autoMode.allow` entries - **Hook false positives**: names the hook script that blocked harmless commands, since each block counts toward auto mode's fallback to prompts - **Dangerous operations**: keeps them in deny or ask ## Usage ```text /permission-tuner ``` After running, review the suggested changes and apply the ones you want. `autoMode` entries belong in `~/.claude/settings.json`.
© Rohit Ghumare · MIT · rohitg00/pro-workflow