--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.
If the sign-in screen itself cannot open, Claude Code says so and shows the usual sign-in error instead.
The 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.
If sign-in goes wrong while starting a cloud session, you get a way to sign in and continue rather than a dead end.
tengu_remote_backend Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.305: 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.
Read once, for one account on one subscription tier, against v2.1.305. It isn't a statement about your account. What a flag value here can and cannot tell you
> `--cloud` creates cloud sessions. `--remote-control` is unrelated: it lets you monitor and steer a local CLI session from claude.ai or the Claude app. See [Remote Control](/docs/en/remote-control).see the edit
| `--remote-control-session-name-prefix <prefix>` | Prefix for auto-generated session names when no explicit name is set. Defaults to your machine's hostname, producing names like `myhost-graceful-unicorn`. Set `CLAUDE_REMOTE_CONTROL_SESSI…see the edit
--remote on Use Claude Code in the cloud