{"version":"2.1.305","anchor":"cloud-sessions-sign-in-screen-on-auth-failure-existing-ses","canonical_anchor":"cloud-sessions-sign-in-screen-on-auth-failure-existing-ses","heading":"Cloud sessions can open a sign-in screen when sign-in fails","tier":"use","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/cloud-sessions-sign-in-screen-on-auth-failure-existing-ses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Cloud sessions can open a sign-in screen when sign-in fails\n\nIf sign-in fails when starting a `--cloud` session, Claude Code can now show a sign-in screen and carry on instead of only printing an error\n\n**What**\n\n`--cloud` starts a Claude Code session that runs in the cloud rather than on your computer, and `--remote` is an older name for the same flag. When signing in for such a session fails, Claude Code can now open a sign-in screen and then continue into the normal session. Before, it only printed an error.\n\nIf the sign-in screen itself cannot open, Claude Code says so and shows the usual sign-in error instead.\n\nThe error \"Attaching to an existing cloud session is not enabled for your account.\" can now also appear in a second situation when the cloud backend is not available to you. The check for the cloud backend is off unless it is switched on remotely.\n\n**Why**\n\nIf sign-in goes wrong while starting a cloud session, you get a way to sign in and continue rather than a dead end.\n\n- Flag `tengu_remote_backend`: Not enough to say (read for one account on one subscription tier against v2.1.305; this account: no value returned, anonymous baseline: no value returned, compiled default: off) 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: Cloud Sessions\n- Names: `--remote`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}