A new relaunchEnforcementHours setting controls how long a user can keep working on a stale config after the server pushes a change before the app forces a restart dialog. It defaults to 1 hour, is settable from 0 to 336 hours, and only takes effect when set via the remote bootstrap config; it is ignored if set via MDM.
Names in the bundlerelaunchEnforcementHours
Documented inclaude-code/claude-apps-gateway-config
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up relaunchEnforcementHours, on Configuration reference.
| <span id="relaunchenforcementhours" />Configuration relaunch window<br />`relaunchEnforcementHours` | `integer` | MDM + Bootstrap<br />Added in 1.40609.0 | `24` | Hours a user may keep working on the old configuration after a managed-con…third-party/claude-desktop/configuration see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up relaunchEnforcementHours, on Configuration reference.