{"version":"2.1.227","anchor":"remote-device-registration-for-cowork-sessions","canonical_anchor":"remote-device-registration-for-cowork-sessions","heading":"Remote-device registration for cowork sessions","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/remote-device-registration-for-cowork-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Remote-device registration for cowork sessions\n\nRemote sessions can be tied to the exact machine that started them using a per-account signing key.\n\n**What**\n\nA new subsystem mints a P-256 keypair per account, stores it in secure storage, and registers it with your organization so a remote session can be tied to the specific machine that started it. It signs a binding payload when creating a session. Nothing in this build was found to switch the cowork remote-device flow on, so whether you ever reach it is decided elsewhere.\n\n**Details**\n\n- Registration POSTs `display_name`, `platform` and `public_key`; the platform value is hardcoded to \"linux\" regardless of the host operating system.\n- Failures are typed: key not persisted, request failed, not sent, HTTP error, revoked key, registration unavailable, and `cowork_remote_device_limit_reached`.\n- Revoked or unreadable keys are retired and a new one is minted on the next attempt.\n- Telemetry: `device_registry_register` success and failure counters, plus `tengu_device_bind_skipped`, `tengu_device_bind_failed` and `tengu_device_bind_prepared`.\n- If the server accepts a session but does not bind it to this device, Claude retries unbound and reports `silent_drop`.\n\n**Evidence**\n\n`deviceRegistry: device key revoked server-side; a new key will be minted on the next registration`, `\/api\/organizations\/:orgUUID\/cowork\/remote_devices`\n\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}