{"version":"2.1.318","anchor":"cloud-session-create-gets-move-flag-and-self-hosted-start-no","canonical_anchor":"cloud-session-create-gets-move-flag-and-self-hosted-start-no","heading":"Creating a cloud session can return move and self-hosted start details","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/cloud-session-create-gets-move-flag-and-self-hosted-start-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Creating a cloud session can return move and self-hosted start details\n\nA newly created cloud session can now carry a flag saying it may run on a runner, plus a start notice for self-hosted runners\n\n**Unclear.** It is not clear what a user sees or can do with these new session details.\n\n**What**\n\nWhen Claude Code creates a session that runs in the cloud, the session it gets back can now include two new details:\n\n- `mayBeOnARunner`, set when the session is being moved.\n\n- `selfHostedStartNotice`, a notice about starting on a self-hosted runner (a machine you run yourself instead of Anthropic's).\n\nThe error shown when cloud session setup fails still mentions `CLAUDE_CODE_OAUTH_TOKEN` and `CLAUDE_CODE_ORGANIZATION_UUID`.\n\n**Why**\n\nThis appears to be part of moving sessions between Anthropic's cloud and self-hosted runners.\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"}