{"version":"2.1.228","anchor":"teleport-session-listings-include-the-bound-device-id","canonical_anchor":"teleport-session-listings-include-the-bound-device-id","heading":"Teleport session listings include the bound device id","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/teleport-session-listings-include-the-bound-device-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Teleport session listings include the bound device id\n\nRemote teleport sessions listed locally now carry the id of the device they are bound to.\n\n**What**\n\nRemote teleport sessions mapped into the local session shape now carry a bound device identifier, lower-cased, alongside the existing status and context fields.\n\n**Evidence**\n\n`bound_device_uuid`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}