Piped input no longer silently overrides a task description you passed to --cloud.
What's wrong with this entry?
Giving --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.
- The error for public projects now tells you to drop
--environmentinstead of mentioning Anthropic-managed environments.
Error: --environment with --cloud <description> cannot also take piped stdin. Pass the task as the description, or drop --cloud.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Whitespace-only prompts are rejected for
--cloudand--environmentBoth mention environment
-
v2.1.221
Headless MCP startup wait reworked
Both mention environment
-
v2.1.248
MCP errors sent to Remote Control clients are filtered to a fixed list
Both mention environment