Unclear Which other input must be present for an empty --cloud to be accepted is not clear.
What
These changes affect starting a cloud session, which runs Claude Code on remote machines instead of your own, with --cloud and --environment.
--environmentis now parsed as a pool, an id (startingenv_) or a name. Only a pool id actually works so far: anything else still returns the error that--environmentexpects a self-hosted environment id (ccpool_...).- A cloud run without the interactive screen now resolves an environment query, if one is given, before creating the session. If that fails it stops with an error. If it succeeds it adds a notice, unless the chosen environment moved.
- The
--cloudhint text and flag are now chosen when an environment query is given, not only when a pool is. - When
--cloudis given with no value, the task can now come from the prompt you passed separately, such as piped input or a positional argument. The--cloud requires a descriptionerror and the message about--cloudnot also taking piped input are kept. - The non-interactive error asking you to drop
--cloud/--remotewith a description now applies only when the environment is a pool.
Why
More ways of calling claude --cloud are accepted without the interactive screen. Choosing an environment by name or env_ id is not usable yet, so keep using ccpool_ ids for now.
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.295: 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.295. It isn't a statement about your account. What a flag value here can and cannot tell you
Which other input must be present for an empty `--cloud` to be accepted is not clear.