{"version":"2.1.285","anchor":"tengu-cobalt-awning-auth-cache-clock-for-remote-sessions","canonical_anchor":"tengu-cobalt-awning-auth-cache-clock-for-remote-sessions","heading":"Remote sessions can track when the last full sign-in check happened","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/tengu-cobalt-awning-auth-cache-clock-for-remote-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Remote sessions can track when the last full sign-in check happened\n\nRemote sessions gain bookkeeping for the time of the last full sign-in check before model requests, off unless a server value is set\n\n**Unclear.** What uses the recorded time, beyond keeping track of it, is not known.\n\n**What**\n\nClaude Code now has code that records when the last full check of your sign-in happened before it sends requests to the model. It only runs when `CLAUDE_CODE_REMOTE` is set, which marks a session running remotely.\n\nThe interval comes from a server-side setting read as a number of seconds. A negative value or anything that is not a number turns it off, and when the server sends nothing the code falls back to off.\n\n**Why**\n\nThis is groundwork for an interval the server can set. You will not notice anything unless the server supplies a value.\n\n- Flag `tengu_cobalt_awning`: Not enough to say (read for one account on one subscription tier against v2.1.285; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}