{"version":"2.1.246","anchor":"startup-drops-a-storage-backend-built-for-a-different-claude","canonical_anchor":"startup-drops-a-storage-backend-built-for-a-different-claude","heading":"Startup drops a storage backend built for a different CLAUDE_CONFIG_DIR","tier":"notice","area":"Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/startup-drops-a-storage-backend-built-for-a-different-claude","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Startup drops a storage backend built for a different CLAUDE_CONFIG_DIR\n\nStartup warns and skips a storage backend built against a different CLAUDE_CONFIG_DIR.\n\n**What**\n\nStartup 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.\n\n**Details**\n\n- Only reachable when the v5 storage backend is in use.\n- The same startup path now also primes stored-login credentials as a step after the fast-path credential prime.\n\n**Evidence**\n\n`where the v5 storage backend was built at start-up; init() loads its config without it`\n\n- Area: Configuration\n- Names: `CLAUDE_CONFIG_DIR`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}