The cloud-session conflict error now blames --environment, the flag you actually typed.
What's wrong with this entry?
When a self-hosted pool is selected, the cloud-session flag conflict error now blames --environment rather than --cloud, and drops the claude.ai/code reattach hint that did not apply.
--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