Error / Message
Git commands keep prompting for permission
Git commands go through the same permission system as any shell command — without a specific rule, each one (or each new git subcommand) can prompt individually.
This is the general permission system working as designed, not something specific to git — any shell command without an explicit rule behaves the same way.
The fix isn't disabling permission checks broadly; it's adding a scoped rule for the specific git operations you trust running automatically (status, diff, log are usually safe to auto-approve; push and force operations are worth keeping a manual gate on).
See /permissions for where these rules live, and the toolkit's own pre-commit lint hook for an example of enforcing a check specifically around commits rather than gating every git command equally.
Add a scoped rule for safe git subcommands via /permissions, rather than approving broadlyFrequently asked questions
What does "Git commands keep prompting for permission" mean in Claude Code?
Git commands go through the same permission system as any shell command — without a specific rule, each one (or each new git subcommand) can prompt individually.
How do I fix it?
Try: Add a scoped rule for safe git subcommands via /permissions, rather than approving broadly
Is this something to worry about?
See /permissions for where these rules live, and the toolkit's own pre-commit lint hook for an example of enforcing a check specifically around commits rather than gating every git command equally.
Is this covered in the Claude Code Toolkit?
Yes — Git commands keep prompting for permission and patterns like it are part of the full command, hook, and template pack included with a Claude Code Toolkit subscription.
Want the full command, hook, and template pack?
This is one pattern out of the full Claude Code Toolkit — subscribe for the complete set, plus everything we add going forward.
Subscribe to the toolkit — $79/mo