{"version":"2.1.232","anchor":"project-no-longer-starts-a-cloud-session","canonical_anchor":"project-no-longer-starts-a-cloud-session","heading":"--project no longer starts a cloud session","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/project-no-longer-starts-a-cloud-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### --project no longer starts a cloud session\n\nPassing --project alone won't start a cloud session; --ref and --on-branch now need --cloud or --environment.\n\n**What**\n\n`--ref` and `--on-branch` now require `--cloud` or `--environment` even when `--project` is given, and the resulting error adds a clause explaining that `--project` alone is not enough. The remote-project field was dropped from the session options that get built.\n\n**Details**\n\n- `--project` still applies to Remote Control, where a session's project is fixed at creation: disconnect first, then re-run `\/remote-control --project` to start a new one.\n\n**Evidence**\n\n`--project no longer starts cloud sessions`\n\n- Area: Cloud Sessions\n- Names: `--project`, `--ref`, `--on-branch`, `--cloud`, `--environment`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}