A new helper checks whether the project's local settings file, .claude/settings.local.json, is tracked in the git index, caching the result per working directory. Claude Code now records this per project as localSettingsSeenGitTracked and uses it to decide whether localSettings should also be honored during permission resolution.
Names in the bundle.claude/settings.local.json
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on How Claude remembers your project touched a line naming .claude/settings.local.json after this was published.
When you set it in a project's `.claude/settings.json` or `.claude/settings.local.json`, Claude Code honors it under the same [workspace trust rule as hooks in settings files](/docs/en/permissions#what-runs-before-you-trust-a-folder). Whil…memory see the edit
Confirmed since
Anthropic's documentation has since written up .claude/settings.local.json, on Agent SDK reference - TypeScript.
| `updateSettings(source, settings)` | Merges settings into the project's local settings file, `.claude/settings.local.json`; they take effect on the next request. Accepts only `source: 'localSettings'` and an allowlisted key set, currentl…agent-sdk/typescript see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up .claude/settings.local.json, on Agent SDK reference - TypeScript.
Anthropic's release notes agree
Fixed settings in a .claude/ folder created after startup not being picked up until restart