{"version":"2.1.281","anchor":"managed-config-schema-runtime-defaults-now-include-internal","canonical_anchor":"managed-config-schema-runtime-defaults-now-include-internal","heading":"Managed-config schema: runtime defaults now include internal keys; diff of non-hot-applied keys added","tier":"internal","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/managed-config-schema-runtime-defaults-now-include-internal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Managed-config schema: runtime defaults now include internal keys; diff of non-hot-applied keys added\n\nManaged-config defaults now cover internal keys, and new helpers list changed keys that cannot apply without a restart\n\n**Unclear.** The finding does not confirm that the list of non-hot-applied keys is used to decide when a restart is needed.\n\n**What**\n\nWhen Claude Code fills in default values for managed configuration (settings an organisation controls), it now includes internal keys as well. New helpers were added:\n\n- One writes configuration as JSON in a fixed, standard form, so two copies can be compared.\n\n- One lists changed keys that are not marked `hotApplied`, meaning they do not take effect while Claude Code is running.\n\n- A `failClosedValue` matcher was also added.\n\n**Why**\n\nThese changes let Claude Code tell which configuration changes cannot take effect straight away. In practice nothing visible changes yet.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}