{"version":"2.1.248","anchor":"remote-sessions-notice-their-own-requests-coming-back","canonical_anchor":"remote-sessions-notice-their-own-requests-coming-back","heading":"Remote sessions notice their own requests coming back","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-sessions-notice-their-own-requests-coming-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote sessions notice their own requests coming back\n\nRemote sessions spot their own echoed requests and renew device proof when unverified.\n\n**What**\n\nA remote session client now recognises when a control request it sent is echoed back to it from another source, checks the device attestation status on that frame, and renews its device proof when the status is unverified.\n\n**Details**\n\n- The client keeps the uuids of its own requests and only takes this path when the returned uuid matches one it sent; previously such frames were dropped.\n- A new echo callback fires and is wired to a one-shot handler on the pending request.\n- No gate; reachable on any remote session connection.\n\n**Evidence**\n\n`echoed from source=`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}