{"version":"2.1.224","anchor":"cloud-cli-piped-stdin-no-longer-silently-overrides-a-task-de","canonical_anchor":"cloud-cli-piped-stdin-no-longer-silently-overrides-a-task-de","heading":"cloud CLI: piped stdin no longer silently overrides a task description","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/cloud-cli-piped-stdin-no-longer-silently-overrides-a-task-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### cloud CLI: piped stdin no longer silently overrides a task description\n\nPiped input no longer silently overrides a task description you passed to --cloud.\n\n**What**\n\nGiving `--cloud` a task description while also passing `--environment` and piping stdin is now rejected instead of letting stdin quietly win. When an environment is given, creating the session also prints its id.\n\n**Details**\n\n- The error for public projects now tells you to drop `--environment` instead of mentioning Anthropic-managed environments.\n\n**Evidence**\n\n`Error: --environment with --cloud <description> cannot also take piped stdin. Pass the task as the description, or drop --cloud.`\n\n- Area: Cloud Sessions\n- Names: `--cloud`, `--environment`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}