{"version":"2.1.317","anchor":"managed-settings-explains-why-parent-settings-are-not-appli","canonical_anchor":"managed-settings-explains-why-parent-settings-are-not-appli","heading":"Claude Code now records why parent settings were not applied","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/managed-settings-explains-why-parent-settings-are-not-appli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Claude Code now records why parent settings were not applied\n\nWhen settings from an embedding app are dropped, Claude Code now records why, such as admin managed settings that do not merge\n\n**What**\n\nWhen an app embeds Claude Code, it can pass in its own settings, called parent settings. Claude Code now records a reason when it does not apply them:\n\n- managed settings from an administrator apply and do not set `parentSettingsBehavior` to merge\n\n- nothing blocked the parent settings, but none of their keys were kept\n\n**Why**\n\nThis makes it possible to work out why settings from an app were ignored.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}