Combining --bg and --environment now explains they are different backends and shows the right command.
What's wrong with this entry?
Passing both now says the two are different backends and shows the direct command to run instead, rather than reusing the older --cloud wording.
--bg and --environment are different backends. Use claude -p '<task>' --environment <id> directly to start a session on the environment.
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