{"version":"2.1.299","anchor":"cloud-cloud-and-tengu-remote-backend-handling","canonical_anchor":"cloud-cloud-and-tengu-remote-backend-handling","heading":"Internal rework of how --cloud sessions are started","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/cloud-cloud-and-tengu-remote-backend-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Internal rework of how `--cloud` sessions are started\n\nThe code that starts cloud sessions with `--cloud` was reorganised, with no change you can see\n\n**What**\n\nThe code that starts a cloud session with `--cloud` was reorganised. The remote setting it depends on still defaults to off when the server sends nothing.\n\n**Why**\n\nThe change looks like internal tidying, and nothing points to a difference in how `--cloud` behaves.\n\n- Flag `tengu_remote_backend`: Not enough to say (read for one account on one subscription tier against v2.1.299; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}