{"version":"2.1.288","anchor":"auth-warm-check-now-has-trigger-types-scheduling-and-decisi","canonical_anchor":"auth-warm-check-now-has-trigger-types-scheduling-and-decisi","heading":"Sign-in check can now run on a timer, not only at turn start","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/auth-warm-check-now-has-trigger-types-scheduling-and-decisi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Sign-in check can now run on a timer, not only at turn start\n\nClaude Code's early check that your sign-in is still fresh can now be scheduled ahead of time as well as at the start of a turn\n\n**Unclear.** Whether this warm-up is on by default could not be determined.\n\n**What**\n\nClaude Code can check your sign-in with the server early, so it is still fresh when a request needs it. Before, it made a single check and then ran this warm-up when the sign-in was stale. The warm-up now records what started it:\n\n- `turn_start`: Claude is starting a turn.\n\n- `lapse_timer`: a timer set for when the sign-in is about to lapse.\n\n- `owner_present`: the owner of the session is present.\n\nEach time, Claude Code decides whether to run the warm-up. It may be off, already running, paused, not needed because the sign-in is fresh, scheduled for later, or run now. If a later run is scheduled, a timer starts it.\n\n**Why**\n\nThe sign-in can be refreshed before you send a request, not only when a turn begins.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}