What
Startup now verifies that CLAUDE_CONFIG_DIR still names the config home the v5 storage backend was created against. If it does not, Claude Code warns and loads your config without that backend for this run, instead of reading from the wrong config home.
Details
- Only reachable when the v5 storage backend is in use.
- The same startup path now also primes stored-login credentials as a step after the fast-path credential prime.
Evidence
where the v5 storage backend was built at start-up; init() loads its config without it
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleCLAUDE_CONFIG_DIR
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 Customize sessions in self-hosted environments touched a line naming CLAUDE_CONFIG_DIR after this was published.
| `CLAUDE_CONFIG_DIR` | Per-session Claude config directory, written at session start from the snapshot of the runner host's config that the runner captures at startup; see [Permissions and tool approval](#permissions-and-tool-approval). W…self-hosted-environments-configuration see the edit
Confirmed since
Anthropic's documentation has since written up CLAUDE_CONFIG_DIR, on Claude Code changelog.
* \[VSCode] Fixed the session list, settings toggles, and chat tabs when `CLAUDE_CONFIG_DIR` is set in a settings file or the `environmentVariables` settingchangelog see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up CLAUDE_CONFIG_DIR, on Claude Code changelog.