{"version":"2.1.312","anchor":"oauth-401-recovery-handles-token-refresh-differently-in-clou","canonical_anchor":"oauth-401-recovery-handles-token-refresh-differently-in-clou","heading":"Cloud session requests can retry after a sign-in error even when the token is unchanged","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/oauth-401-recovery-handles-token-refresh-differently-in-clou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Cloud session requests can retry after a sign-in error even when the token is unchanged\n\nAfter a sign-in error on a cloud session request, Claude Code can now retry in some cases even when its sign-in token did not change\n\n**Unclear.** It is not clear which cloud requests carry the setting that allows the retry.\n\n**What**\n\nA cloud session runs on remote machines instead of your own computer. When one of its requests is rejected because the sign-in was not accepted (an HTTP 401 error), Claude Code tries to recover a working sign-in token. Before, if the token it got back was the same as before, it gave up. Now a setting carried on the request can tell Claude Code to retry anyway, even when the token has not changed.\n\n**Why**\n\nThe aim is sturdier sign-in handling for cloud sessions.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}