{"version":"2.1.227","anchor":"cloud-sessions-can-be-bound-to-the-machine-that-created-them","canonical_anchor":"cloud-sessions-can-be-bound-to-the-machine-that-created-them","heading":"Cloud sessions can be bound to the machine that created them","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/cloud-sessions-can-be-bound-to-the-machine-that-created-them","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Cloud sessions can be bound to the machine that created them\n\nCloud sessions can be bound to your machine so local tools only run there, currently gated off.\n\n**What**\n\nNew machinery ties a remote or cloud session to the device that started it, so local tools only run for that machine. Session creation registers the machine and signs a proof of the binding. It is gated on `tengu_violin_wood`, checked asynchronously, and any error means the session is simply not bound.\n\n**Details**\n\n- Session creation is refused outright in combinations not yet supported, reported as `device_bind_project_unsupported` and `device_bind_agent_unsupported`.\n- Binding failures degrade to an unbound session and emit `tengu_device_bind_skipped` or `tengu_device_bind_failed`.\n- Three new server rejection causes are recognised: `bind_attestation_stale`, `bound_session_unattested_write`, and `untrusted_device`.\n\n**Evidence**\n\n`bound_session_unattested_write`\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.227; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) 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: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}