{"version":"2.1.321","anchor":"host-owned-config-dir-unparseable-claudejson-no-longer","canonical_anchor":"host-owned-config-dir-unparseable-claudejson-no-longer","heading":"Apps that manage Claude Code's config folder survive a broken ~\/.claude.json","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/host-owned-config-dir-unparseable-claudejson-no-longer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Apps that manage Claude Code's config folder survive a broken ~\/.claude.json\n\nWith CLAUDE_CODE_HOST_OWNED_CONFIG_DIR set, a ~\/.claude.json that cannot be read no longer stops Claude Code; it starts on defaults\n\n**What**\n\nWhen another application starts Claude Code and owns its configuration folder, it names that folder with `CLAUDE_CODE_HOST_OWNED_CONFIG_DIR`. In that case, if the global configuration file (`~\/.claude.json`) cannot be read because it is damaged, Claude Code now starts with default settings and prints a notice. Before, it stopped with an error.\n\nThe next time Claude Code saves its settings, it overwrites the damaged file.\n\n**Why**\n\nDesktop apps and other programs that embed Claude Code can recover from a corrupt configuration file. Anything left in the damaged file is lost once the new save replaces it.\n\n- Area: Settings\n- Names: `CLAUDE_CODE_HOST_OWNED_CONFIG_DIR`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}