{"version":"2.1.315","anchor":"session-archived-check-retries-after-a-401-and-shares-one-in","canonical_anchor":"session-archived-check-retries-after-a-401-and-shares-one-in","heading":"Remote sessions recover when the archived check hits an expired login","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/session-archived-check-retries-after-a-401-and-shares-one-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Remote sessions recover when the archived check hits an expired login\n\nThe check for whether a remote session was archived now refreshes your login first and retries once after an authentication error\n\n**What**\n\nIn a remote session, which is a Claude Code session running on another machine, Claude Code checks whether the session has been archived. That check now refreshes your login credentials before it runs. If the server rejects it with a 401 error, meaning your login was not accepted, Claude Code refreshes the login and tries once more.\n\nIf several parts of Claude Code ask at the same moment, they now share one request instead of each sending its own. In some situations the check is skipped altogether. Before, the check used a stored login and did not retry.\n\n**Why**\n\nRemote sessions should fail less often for no real reason when a login token expires during the session.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}