{"version":"2.1.312","anchor":"cloud-headless-sessions-gain-pool-correlation-and-no-monore","canonical_anchor":"cloud-headless-sessions-gain-pool-correlation-and-no-monore","heading":"Cloud sessions take a pool, a correlation ID and a no-monorepo option","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/cloud-headless-sessions-gain-pool-correlation-and-no-monore","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Cloud sessions take a pool, a correlation ID and a no-monorepo option\n\nCreating a cloud session can now pass a pool, a correlation ID and a no-monorepo option, plus a notice naming an agent that needs a repository\n\n**Unclear.** It is not clear which commands or options let you set these values, or whether they are in use yet.\n\n**What**\n\nWhen Claude Code creates a session that runs in the cloud, it can now pass three more details:\n\n- a pool ID\n\n- a correlation ID\n\n- a no-monorepo option, which also stops your settings from being sent to the cloud session\n\nA cloud session can also carry a notice saying that a particular agent requires a repository, in the form \"The agent \"name\"\". The rules for launching cloud sessions can take a launch folder for the pool and attach that agent and its notice.\n\n**Why**\n\nCloud sessions gain more options for how they are started. With the no-monorepo option, your local settings are not forwarded to the cloud session.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}