{"version":"2.1.311","anchor":"cloud-session-creation-retries-once-on-401-via-bearer-recove","canonical_anchor":"cloud-session-creation-retries-once-on-401-via-bearer-recove","heading":"Starting a cloud session retries once when your sign-in has expired","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/cloud-session-creation-retries-once-on-401-via-bearer-recove","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Starting a cloud session retries once when your sign-in has expired\n\nWhen creating a cloud session is refused as unauthorised, Claude Code can refresh its sign-in token and try once more\n\n**What**\n\nWhen Claude Code asks to create a cloud session (one that runs on Anthropic's machines) and the server answers 401, meaning it was not authorised, Claude Code no longer simply reports the failure. Where a way to recover the sign-in token is available, it recovers the token and sends the request one more time. If that second request is also refused, it starts recovery again in the background.\n\n**Why**\n\nAn expired token is less likely to make session creation fail for no good reason.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}