--bg / --pool Conflict Error Message Improved

What

The error shown when combining --bg with another backend flag now distinguishes between --pool and --cloud.

Details

Using --bg with --pool: "Use claude -p '<task>' --pool <pool_id> directly to start a session on the pool."
Using --bg with --cloud: "Use claude --cloud '<task>' directly to start a cloud session."

Evidence

Updated error message function (search for "--bg and --pool are different backends")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

The build it came inv2.1.172

10 Jun 2026 · 22 entries, this one is #13.

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--pool
Start a cloud session on your own environment with claude --environment, plus hidden --ref and --on-branch companions.
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.