{"version":"2.1.318","anchor":"config-reads-unparseable-file-backup-tracking-and-queued-re","canonical_anchor":"config-reads-unparseable-file-backup-tracking-and-queued-re","heading":"Startup handles a corrupt or missing config file more carefully","tier":"notice","area":"Configuration","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/config-reads-unparseable-file-backup-tracking-and-queued-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Startup handles a corrupt or missing config file more carefully\n\nClaude Code now tracks a backup made when its config file cannot be read at startup, and whether it left an unreadable file alone\n\n**What**\n\nYour config file is where Claude Code stores its settings and what it knows about your projects. At startup, Claude Code now keeps track of:\n\n- Where it saved a backup when the config file could not be read.\n\n- Whether it left an unreadable config file untouched.\n\nA check on project trust or settings also now requires that no entry for the project exists when an earlier read found no config file at all.\n\n**Why**\n\nThis is likely meant to stop Claude Code from overwriting or misreading a damaged config file when it starts.\n\n- Area: Configuration\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}