{"version":"2.1.293","anchor":"bootstrap-intake-retired-key-effects-loopback-fail-closed","canonical_anchor":"bootstrap-intake-retired-key-effects-loopback-fail-closed","heading":"Managed settings handle retired keys and local addresses more strictly","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/bootstrap-intake-retired-key-effects-loopback-fail-closed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Managed settings handle retired keys and local addresses more strictly\n\nManaged settings now explain what a retired setting did, and a local address on a fail-closed setting falls back to the safe value\n\n**Unclear.** It is not settled whether this applies to the Claude Code command-line tool or only to code bundled with the desktop app.\n\n**What**\n\nManaged settings are ones an organization's administrators push to Claude Code. The way Claude Code takes them in changed:\n\n- The message for a retired setting, one no longer read, now also says what that setting did.\n\n- A loopback address is one that points back at your own machine, such as `localhost`. If one is given for a setting that has a fail-closed value, Claude Code now uses that value instead of deleting the setting. A fail-closed value is the safe choice used when something cannot be trusted.\n\n- Whether a loopback address is allowed on a hybrid channel is now decided per setting.\n\n- Consent entries skip empty lists and now keep the labels they used to have.\n\n**Why**\n\nThis tightens how Claude Code accepts managed configuration, so a doubtful setting falls back to its safe value instead of disappearing.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}