{"version":"2.1.242","anchor":"auto-update-checks-are-throttled-within-a-long-running-proce","canonical_anchor":"auto-update-checks-are-throttled-within-a-long-running-proce","heading":"Auto-update checks are throttled within a long-running process","tier":"notice","area":"Updater","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/auto-update-checks-are-throttled-within-a-long-running-proce","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Auto-update checks are throttled within a long-running process\n\nLong-running sessions stop making redundant auto-update checks; there is no flag for it.\n\n**What**\n\nAn auto-update check is now skipped if one ran recently, so a long-lived session stops making redundant checks. The skip is logged with how many seconds ago the last check ran. There is no flag.\n\n**Details**\n\n- Updater state (time of the last auto-update check, an update-restore failure marker, and minted preserved inodes) moved from module-level globals into one per-process object.\n- The self-heal paths that restore a missing `claude` binary from a preserved `<exe>.old.<timestamp>` copy now receive that state explicitly instead of reading globals.\n- The npm install and uninstall shell-outs now resolve the home directory through a helper rather than calling `os.homedir()` directly.\n\n**Evidence**\n\n`auto-update check throttled (last check `\n\n- Area: Updater\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}