Starting a cloud session with --cloud (or --remote, its deprecated alias, or --environment) can keep the session open in your terminal. If it would, but Claude Code cannot read your keyboard there, for example because input is piped in from another program, it now stops with an error before creating any session:
"No cloud session was created or opened: it would open in this terminal and need the keyboard."
The error is followed by one of three explanations:
- You are on Windows.
- The
CIenvironment variable is set, which marks an automated build system. - The terminal device /dev/tty is not available.
Whether the session stays open in your terminal depends partly on a setting that is off unless it is switched on remotely.
Running a cloud launch from a script or automated job now fails straight away with a clear message instead of hanging or misbehaving, and leaves no unused session behind.
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.287: 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.287. It isn't a statement about your account. What a flag value here can and cannot tell you
The exact conditions that decide when the session would stay open in the terminal are not clear.