{"version":"2.1.301","anchor":"cloud-launch-passes-explicit-ref-and-device-too-old-state","canonical_anchor":"cloud-launch-passes-explicit-ref-and-device-too-old-state","heading":"Cloud session launch records which ref you chose and how","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/cloud-launch-passes-explicit-ref-and-device-too-old-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Cloud session launch records which ref you chose and how\n\nCreating a cloud session now notes the ref you named and whether it came from --on-branch or --ref, plus a new file sync state\n\n**Unclear.** Nothing shows how cloudSessionsByDefault is set or what it changes.\n\n**What**\n\nWhen Claude Code creates a cloud session, it now records the ref you named (a branch or other point in your git history) and which flag supplied it, `--on-branch` or `--ref`.\n\n- File sync status can now be `device_too_old`, as well as on or off.\n\n- Launch options gain a `cloudSessionsByDefault` field.\n\n**Why**\n\nThese details feed into how cloud session creation is recorded and routed.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}