{"version":"2.1.229","anchor":"whitespace-only-prompts-are-rejected-for-cloud-and-environme","canonical_anchor":"whitespace-only-prompts-are-rejected-for-cloud-and-environme","heading":"Whitespace-only prompts are rejected for --cloud and --environment","tier":"notice","area":"CLI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/whitespace-only-prompts-are-rejected-for-cloud-and-environme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Whitespace-only prompts are rejected for `--cloud` and `--environment`\n\nWhitespace-only prompts on `--cloud` and `--environment` are rejected instead of sent empty.\n\n**What**\n\nA prompt consisting only of spaces or newlines is now treated as no prompt at all on both non-interactive paths, so you get the existing \"requires a prompt\" error instead of an empty request being sent.\n\n**Evidence**\n\n`Error: non-interactive --cloud <session_id> requires a prompt (positional or stdin).`\n\n- Area: CLI\n- Names: `--cloud`, `--environment`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}