{"version":"2.1.260","anchor":"auto-update-enforcement-window-documented-idle-wait-behavio","canonical_anchor":"auto-update-enforcement-window-documented-idle-wait-behavio","heading":"Auto-update enforcement window: documented idle-wait behavior and interaction with disableAutoUpdates","tier":"use","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/auto-update-enforcement-window-documented-idle-wait-behavio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Auto-update enforcement window: documented idle-wait behavior and interaction with disableAutoUpdates\n\nAuto-update enforcement docs now clarify idle-wait and restart behavior in detail.\n\n`autoUpdaterEnforcementHours` now has a long description clarifying its behavior: it has no effect when `disableAutoUpdates` is set, since the updater never starts. Leaving it blank uses the 72-hour default and waits for at least 10 minutes of machine idle before restarting, whereas setting an explicit value, even 72, restarts once the window elapses regardless of activity. In both cases, restarts still hold off while Claude is mid-task.\n\n- Area: Elsewhere\n- Names: `autoUpdaterEnforcementHours`\n- Tier: Use it now\n- Useful: 1\/5\n- Signal: 1\/5"}