{"version":"2.1.236","anchor":"reporting-a-corrupted-config-can-no-longer-crash-claude-code","canonical_anchor":"reporting-a-corrupted-config-can-no-longer-crash-claude-code","heading":"Reporting a corrupted config can no longer crash Claude Code","tier":"notice","area":"Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/reporting-a-corrupted-config-can-no-longer-crash-claude-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Reporting a corrupted config can no longer crash Claude Code\n\nA corrupted config file now gets reported and backed up without crashing Claude Code.\n\n**What**\n\nThe path that handles a corrupted Claude config file (telemetry for the parse error, backing up the bad file, and the \"Claude configuration file at ... is corrupted\" message) is now wrapped so a failure inside it is logged instead of thrown.\n\n**Details**\n\n- Previously an error while reporting the corruption escaped and could take down the surrounding operation.\n- Failures now log at error level and reporting continues.\n\n**Evidence**\n\n`Could not report the corrupt config: `\n\n- Area: Configuration\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}