Startup warns and skips a storage backend built against a different CLAUDE_CONFIG_DIR.
What's wrong with this entry?
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.
- 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.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
Workflow size guideline gets a default and a policy override
Both mention config configuration
-
v2.1.248
/config now separates a refused setting from a failed save, and hides save detail remotely
Both mention config configuration
-
v2.1.236
Reporting a corrupted config can no longer crash Claude Code
Both mention configuration