{"version":"2.1.287","anchor":"headless-cloud-launch-refuses-sessions-not-recognized-as-clo","canonical_anchor":"headless-cloud-launch-refuses-sessions-not-recognized-as-clo","heading":"--environment cloud sessions gain a --no-monorepo option and a start-up recognition check","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/headless-cloud-launch-refuses-sessions-not-recognized-as-clo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### --environment cloud sessions gain a --no-monorepo option and a start-up recognition check\n\n--no-monorepo now supplies a default --environment and is passed on when the session is created; unrecognised cloud launches now stop with an error\n\n**Unclear.** The command-line spelling of the monorepo option and the exact start-up check are not known.\n\n**What**\n\nThe `--environment` flag creates a new cloud session, meaning a Claude Code session running on a remote machine, on a self-hosted environment. Without the interactive screen, this path now changes in several ways:\n\n- `--no-monorepo`: when the `noMonorepo` option is set, a default environment ID is used when checking `--environment`. Before, the environment came only from the environment or pool options.\n\n- Passed on: `noMonorepo` is sent along with `poolId` when the cloud session is created. The JSON output still returns `pool_id`.\n\n- Start-up check: a cloud session now stops with an error up front if it was not recognised as a cloud launch at start-up. The message says \"this cloud session launch was admitted without being recognised as one at start-up\".\n\n- Error messages about flags that conflict with `--environment`, such as \"--environment cannot be combined with\", are now built from a template.\n\n- The fast start path for tmux and worktrees now calls `configureFastPathGlobalAgents` before checking worktree mode.\n\n**Why**\n\nIf you create cloud sessions with `--environment`, you can pass `--no-monorepo` without naming an environment yourself, and a launch that was not set up as a cloud session now fails clearly instead of running.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}