Clearer error when --bg and --environment are combined

Clearer error when --bg and --environment are combined

Combining --bg and --environment now explains they are different backends and shows the right command.

You'll noticeTier: how much it should matter to you

2Useful: my rating, 1 to 5

1Signal: worth watching, 1 to 5

CLIArea: what it touches

ImprovementsKind: in v2.1.224, 07 Aug 26

ImprovementsSection of the release

What

Passing both now says the two are different backends and shows the direct command to run instead, rather than reusing the older --cloud wording.

Evidence

--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.

Read from

Names in the bundle--bg--environment

The build it came inv2.1.224

7 Aug 2026 · 352 entries, this one is #210.

Either side of it

Open the release →

Names in this entry

cli--bg
Start the session as a background agent and return immediately. Prints the session ID and management commands. Combine with --exec to run a shell command as a background job instead of a Claude session, or with --agent to run a specific subagent. Checks workspace trust for the directory before it starts. Can't be combined with -p/--print; see the error reference
cli--environment
Create a new cloud session that runs on the self-hosted environment with the given ID. Environment IDs start with ccpool_. See --environment dispatch behavior for dispatch behavior and the flag combinations it rejects. Requires Claude Code v2.1.224 or later
cli--cloud
With a task description, create a new cloud session. With a session ID (session_... or cse_...) or a claude.ai/code URL, queue a message into that existing session instead, with -p. See send a follow-up message.

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.