{"version":"2.1.232","anchor":"settings-errors-that-block-startup-no-longer-appear-in-the-i","canonical_anchor":"settings-errors-that-block-startup-no-longer-appear-in-the-i","heading":"Settings errors that block startup no longer appear in the invalid-settings dialog","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/settings-errors-that-block-startup-no-longer-appear-in-the-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Settings errors that block startup no longer appear in the invalid-settings dialog\n\nStartup-blocking settings errors are now reported as fatal rather than listed with the rest.\n\n**What**\n\nErrors marked as startup-fatal are filtered out of the list shown in the invalid-settings dialog, joining the existing exclusions for MCP error metadata and status-only entries. An invalid static settings payload is now one of those fatal cases, and reports that Claude Code will not start until it is fixed.\n\n**Details**\n\n- The policy helpers map now also accepts an optional `default` settings payload.\n\n**Evidence**\n\n`is not a valid static settings payload`\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}