settings.local.json
A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
The runner can warn about or block repo-committed settings that grant access outside the workspace.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.224.
In the changelogs
17Releases whose published page names settings.local.json.
-
v2.1.288
Local settings file is now described as this folder's, not this checkout's
Messages about the local settings file now say "this folder's settings.local.json" instead of "this checkout's settings.local.json"
named in this entry, found in this entry's text
-
v2.1.287
Cloud session hooks panel reworded and gains a plugin hooks section
The panel listing this machine's hooks for a cloud session has shorter text and makes room for a section about plugin hooks
found in this entry's text
-
v2.1.284
Settings files are read from a resolved location
When Claude Code updates or scans settings files, it now works out each file's resolved location before reading it
found in this entry's text
-
v2.1.282
Project settings can only turn telemetry off, and Claude Code now says so
A project's settings can now turn telemetry export off but not on, and a new warning points to
/statusto show which variables appliedfound in this entry's text
-
v2.1.271
Self-hosted runner gains host-config snapshotting for sessions
The self-hosted runner can now snapshot an operator's Claude config and seed it into every session, with a drain-marker mechanism
found in this entry's text
-
v2.1.257
New user-facing errors for cloud session sync and TLS pinning failures
New messages cover sync being switched off because settings.json could not be parsed, and sign-in aborting on a changed TLS certificate.
found in this entry's text
-
v2.1.242
Consent screen explaining what forwarding your hooks to a cloud session means
A consent screen explains what letting cloud sessions run your local hooks means.
found in this entry's text
-
v2.1.232
New environment variable for cloud peer access
CLAUDE_CODE_HARBOR_KITE_CLOUDturns on cloud peer access; otherwise a server flag decides and it's off.found in this entry's text
-
v2.1.224
Runner can refuse repo-committed settings that reach outside the workspace
The runner can warn about or block repo-committed settings that grant access outside the workspace.
found in this entry's text
- v2.1.211
-
v2.1.211
settings.local.json Ownership Verification Before Canonicalization
found in this entry's text
-
v2.1.207
/auto-mode-setup: project settings.local.json Audit
found in this entry's text
-
v2.1.193
Worktree Symlink Safety Checks
found in this entry's text
-
v2.1.121
Symlink Safety Improvements
found in this entry's text
-
v2.1.48
Git Worktree Mode
found in this entry's text
-
v2.1.26
Terminal Tab Title Setting
found in this entry's text
-
v2.0.47
Remote Environment Configuration
found in this entry's text
First cited
3The earliest release whose published evidence quoted settings.local.json was v2.1.121, 27 Apr 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.