{"version":"2.1.315","anchor":"remote-session-archived-check-reuses-a-refreshed-token-and-r","canonical_anchor":"remote-session-archived-check-reuses-a-refreshed-token-and-r","heading":"Remote sessions retry the archived check after an expired login","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/remote-session-archived-check-reuses-a-refreshed-token-and-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Remote sessions retry the archived check after an expired login\n\nChecking whether a remote session is archived now gets a fresh credential and retries once if the sign-in was rejected\n\n**What**\n\nIn a remote session, meaning one that runs on a machine in the cloud, Claude Code checks whether the session has been archived. That check changed in three ways:\n\n- It fetches a current credential instead of using the one the session started with.\n\n- If the server rejects the sign-in, Claude Code signs in again and retries once.\n\n- Checks that overlap share one request instead of each sending their own.\n\nBefore, there was no retry.\n\n**Why**\n\nRemote sessions should report fewer errors about reading the archived status after a login token expires.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}