{"version":"2.1.318","anchor":"config-file-backup-and-empty-file-recovery","canonical_anchor":"config-file-backup-and-empty-file-recovery","heading":"Better recovery when the Claude Code config file is broken or empty","tier":"notice","area":"Configuration","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/config-file-backup-and-empty-file-recovery","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Better recovery when the Claude Code config file is broken or empty\n\nIf the config file is corrupt or empty, Claude Code looks for the best backup and tells you what it did or what to fix\n\n**What**\n\nClaude Code keeps its settings in a config file, `~\/.claude.json`. When that file cannot be read, Claude Code now searches for the best backup copy and tells you what happened. If the file holds broken JSON, the message tells you to fix the JSON in the file or move the file aside to start with default settings.\n\nIf the file is empty and no backup holds anything, Claude Code starts with default settings. If no backup exists, it says so.\n\n**Why**\n\nA damaged config file is easier to recover from, and you are told plainly what Claude Code did with it.\n\n- Area: Configuration\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}