Skip to content

Share Claude Code settings as project settings - #70

Open
torarnv wants to merge 3 commits into
joa23:mainfrom
torarnv:rename-claude-local-settings
Open

Share Claude Code settings as project settings#70
torarnv wants to merge 3 commits into
joa23:mainfrom
torarnv:rename-claude-local-settings

Conversation

@torarnv

Copy link
Copy Markdown

Problem

Claude Code settings for this repo lived in .claude/settings.local.json, a file meant for personal, machine-specific overrides. That meant useful permission entries were not shared with other contributors, and the file had accumulated stale, user-specific entries (like another contributor's binary paths and a broad rm permission) that did not belong in a shared config.

Solution

Rename .claude/settings.local.json to .claude/settings.json so the settings are checked in and shared across the team, and add .claude/settings.local.json to .gitignore for future personal overrides. Along the way, drop the stale, personal permission entries (hardcoded binary paths, a say command, a blanket rm permission) that shouldn't be shared.

The checked-in .claude/settings.local.json was the file Claude Code
reserves for personal, untracked overrides. Rename it to settings.json,
which is the shared project file, and ignore settings.local.json so
personal overrides stay out of the repo.
Pre-approving rm with a wildcard lets any path be deleted without a
prompt. Let it prompt instead.
These name binaries and paths the project no longer has: the binary is
called linear, not linear-agent, and there is no linear-mcp-server or
install-mcp.sh in the repo. Also drop two entries left over from the
upstream author, a hardcoded /Users/joa23 path and a one-off say
command.
Sign up for freeto 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

@torarnv