{"version":"2.1.268","anchor":"managed-settings-notices-surfaced-separately-from-errors","canonical_anchor":"managed-settings-notices-surfaced-separately-from-errors","heading":"Managed-settings 'notices' surfaced separately from errors","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/managed-settings-notices-surfaced-separately-from-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Managed-settings 'notices' surfaced separately from errors\n\nManaged-settings startup output now separates non-error notices from actual errors\n\n**Unclear.** Whether the tengu_managed_settings_validation_errors gate is on for any account is unread, so nothing can be said about its current state.\n\n**What**\n\nWhen Claude Code starts up and reports on managed settings (organization-provided configuration), it now also collects and prints non-error \"notices\" under their own \"Managed settings notices:\" heading, separate from the existing reporting of fatal errors and invalid entries.\n\n**Why**\n\nThis lets Claude Code flag things worth knowing about managed settings without implying something is actually broken, and keeps genuine errors from being buried among informational notices.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}