{"version":"2.1.224","anchor":"clearer-error-when-bg-and-environment-are-combined","canonical_anchor":"clearer-error-when-bg-and-environment-are-combined","heading":"Clearer error when --bg and --environment are combined","tier":"notice","area":"CLI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/clearer-error-when-bg-and-environment-are-combined","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Clearer error when `--bg` and `--environment` are combined\n\nCombining --bg and --environment now explains they are different backends and shows the right command.\n\n**What**\n\nPassing both now says the two are different backends and shows the direct command to run instead, rather than reusing the older `--cloud` wording.\n\n**Evidence**\n\n`--bg and --environment are different backends. Use `claude -p '<task>' --environment <id>` directly to start a session on the environment.`\n\n- Area: CLI\n- Names: `--bg`, `--environment`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}