{"version":"2.1.228","anchor":"remote-sessions-can-be-pinned-to-a-single-device","canonical_anchor":"remote-sessions-can-be-pinned-to-a-single-device","heading":"Remote sessions can be pinned to a single device","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/remote-sessions-can-be-pinned-to-a-single-device","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Remote sessions can be pinned to a single device\n\nA remote session can be pinned to one device, refusing attach from anywhere else.\n\n**What**\n\nAttaching to a remote session now checks first whether that session is bound to one device, and registers only when egress is available, an account uuid is present and the local device id matches. Every outcome is reported as `tengu_device_bind_attach` with a result such as bound, egress, account, no_device_here, other_device, session_unbound or session_unreadable. The whole check sits behind an enable predicate; when it is false or throws, the result is `disabled`. Nothing in the build sets that predicate's effective value, so it is decided outside the source.\n\n**Evidence**\n\n`tengu_device_bind_attach`\n\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}