{"version":"2.1.227","anchor":"cloud-sessions-explain-why-they-are-not-bound-to-your-machin","canonical_anchor":"cloud-sessions-explain-why-they-are-not-bound-to-your-machin","heading":"Cloud sessions explain why they are not bound to your machine","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/cloud-sessions-explain-why-they-are-not-bound-to-your-machin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Cloud sessions explain why they are not bound to your machine\n\nWhen a cloud session cannot bind to your machine, you now get a plain reason why.\n\n**What**\n\nWhen a newly created cloud session cannot be tied to the local device, which is what turns off local tools, Claude Code now prints a plain reason instead of leaving it unexplained. Covered cases are device registration failure, hitting the device limit, clock skew, not being logged in, the feature being off server-side, and the server silently dropping the binding.\n\n**Evidence**\n\n`Not bound to this machine (local tools off): `\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}