{"version":"2.1.281","anchor":"managed-config-package-exports-new-restart-and-docs-helpers","canonical_anchor":"managed-config-package-exports-new-restart-and-docs-helpers","heading":"Managed-config package exports new restart and docs helpers","tier":"internal","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/managed-config-package-exports-new-restart-and-docs-helpers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Managed-config package exports new restart and docs helpers\n\nThe managed-config module now exports helpers for settings that need a restart, a config reference link, and a default relaunch enforcement period\n\n**Unclear.** The evidence shows the names being exported but not where they are used or what a user would see.\n\n**What**\n\nManaged configuration is settings that an organisation's administrator applies centrally. The part of Claude Code that handles it now makes these names available to other parts of the program:\n\n- `changedKeysNeedingRestart`\n\n- `canonicalJson`\n\n- `RELAUNCH_ENFORCEMENT_DEFAULT_HOURS`\n\n- `CONFIG_REFERENCE_URL`\n\n- `configReferenceUrl`\n\n- `SSH_CLIENT_UNREADABLE_STAND_IN`\n\n**Why**\n\nFrom the names, these relate to detecting which changed settings only take effect after a restart, to a default number of hours for enforcing a relaunch, and to a link to the configuration reference. The finding does not show any of them being used yet, so nothing visible to a user changes from this alone.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}