Skip to content

Add .claude/settings.json with auto permission mode #513

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jahooma merged 1 commit into from
Apr 19, 2026
+5 −0
Merged

Add .claude/settings.json with auto permission mode #513

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .claude/settings.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"permissions": {
"defaultMode": "auto"
Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps bot Apr 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 security Auto mode applied to all contributors without explicit opt-in

Setting defaultMode: "auto" in the shared .claude/settings.json means every contributor who uses Claude Code in this repo will be placed in auto permission mode automatically, regardless of their personal preference. Auto mode uses a classifier to decide whether to proceed with actions without user confirmation — while safer than --dangerously-skip-permissions, it still bypasses interactive approval for tool calls.

Anthropic's own documentation notes that "a checked-in repo could otherwise inject its own allow rules" as the reason why autoMode classifier configuration is excluded from shared project settings. The defaultMode key is still honoured from shared settings, however.

Consider whether this should live in .claude/settings.local.json (which should be gitignored) so each contributor consciously opts in, rather than inheriting it silently from the repo. Alternatively, document the rationale in the PR/README so contributors are aware.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

}
}
Loading