{"version":"2.1.248","anchor":"remote-desktop-accepted-as-a-session-origin","canonical_anchor":"remote-desktop-accepted-as-a-session-origin","heading":"Remote desktop accepted as a session origin","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-desktop-accepted-as-a-session-origin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote desktop accepted as a session origin\n\nDesktop-hosted remote sessions are no longer rejected as an unknown origin.\n\n**What**\n\nSessions identifying themselves as `remote_desktop` are now accepted alongside `remote`, `sdk-cli` and the unnamed default, so a desktop-hosted remote session is no longer rejected as an unknown origin.\n\n**Details**\n\n- The same transport now declares that outbound frames persist and that the host does not own the stdin origin.\n\n**Evidence**\n\n`new Set([\"remote\", \"remote_desktop\", \"sdk-cli\", \"\"])`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}