Skip to content

Keep personal Claude Code permissions out of the repo - #296

Merged
jeyrb merged 1 commit into
mainfrom
chore/claude-settings-convention
Oct 18, 2026
Merged

jeyrb merged 1 commit into
mainfrom
chore/claude-settings-convention

Conversation

@jeyrb

@jeyrb jeyrb commented Oct 18, 2026

Copy link
Copy Markdown
Contributor

Removes .claude/settings.json: it only held permissions that built up across sessions (local paths, one-off commands, broad rules), and nothing project-wide. Gitignores .claude/settings.local.json so they stay local in future.

Project-scope .claude/settings.json permissions apply to anyone who opens Claude Code in a clone, so accumulated "always allow" rules belong in the gitignored settings.local.json. Convention agreed in rhizomatics/hq-private#23, now in project standards.

Before merging, in your local clone: mv .claude/settings.json .claude/settings.local.json to keep your personal rules (for datalab, keep the hook in settings.json and move only the extra permissions).

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jeyrb
jeyrb merged commit 776fa0a into main Oct 18, 2026
18 checks passed
@jeyrb
jeyrb deleted the chore/claude-settings-convention branch October 18, 2026 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant