{"version":"2.1.248","anchor":"session-rename-after-device-binding-is-signed","canonical_anchor":"session-rename-after-device-binding-is-signed","heading":"Session rename after device binding is signed","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/session-rename-after-device-binding-is-signed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Session rename after device binding is signed\n\nThe automatic session rename after device binding is now signed.\n\n**What**\n\nThe automatic session rename that follows session creation now attaches an event signer derived from the device binding, and only when the binding succeeded.\n\n**Evidence**\n\n`tengu_device_bind_title_latched`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}