{"version":"2.1.224","anchor":"flag-conflict-error-names-the-flag-you-actually-used","canonical_anchor":"flag-conflict-error-names-the-flag-you-actually-used","heading":"Flag-conflict error names the flag you actually used","tier":"notice","area":"CLI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/flag-conflict-error-names-the-flag-you-actually-used","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Flag-conflict error names the flag you actually used\n\nThe cloud-session conflict error now blames --environment, the flag you actually typed.\n\n**What**\n\nWhen 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.\n\n**Evidence**\n\n`--environment`\n\n- Area: CLI\n- Names: `--environment`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}