{"version":"2.1.288","anchor":"cloud-environment-error-text-now-chosen-by-a-helper","canonical_anchor":"cloud-environment-error-text-now-chosen-by-a-helper","heading":"Cloud session error messages now name the flag you actually used","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/cloud-environment-error-text-now-chosen-by-a-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Cloud session error messages now name the flag you actually used\n\nErrors for headless cloud sessions now name the flag you used, --cloud or --environment, instead of always saying --environment\n\n**Unclear.** The exact wording the errors now use in each case is not known.\n\n**What**\n\nClaude Code can start a cloud session from the command line with `--cloud` or `--environment`. It can also run headless, meaning non-interactively, with no chat screen, as in `claude -p`. When you misuse these options, the error messages used to name `--environment` no matter which flag you had typed. Before, a headless run without a prompt said: `Error: non-interactive --environment requires a prompt (positional or stdin).`\n\n- The flag name in these errors is now filled in from the flag you actually used, rather than hardcoded as `--environment`.\n\n- The text in front of the message is also filled in and is no longer always `Error: `.\n\n- The message saying an option cannot be combined with `--continue` is built from that same prefix.\n\n**Why**\n\nIf you started a session with `--cloud`, the error now points at `--cloud` instead of a flag you never typed, so it is easier to see what to fix. Scripts that match on the exact wording of these errors may need updating.\n\n- Area: Cloud Sessions\n- Names: `--continue`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}