{"version":"2.1.281","anchor":"remote-managed-settings-consent-skips-fail-closed-stand-in-v","canonical_anchor":"remote-managed-settings-consent-skips-fail-closed-stand-in-v","heading":"Remote managed-settings consent skips fail-closed stand-in values","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-managed-settings-consent-skips-fail-closed-stand-in-v","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote managed-settings consent skips fail-closed stand-in values\n\nYou are no longer asked to approve placeholder values in remotely managed settings\n\n**What**\n\nSome settings an organisation pushes to Claude Code from a server require your consent before they apply. The list shown for consent now leaves out placeholder values that Claude Code fills in itself as a safe fallback, known as fail-closed stand-ins.\n\n**Why**\n\nYou are only asked to approve values that actually came from your organisation, not stand-ins generated on your machine.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}