{"version":"2.1.285","anchor":"untrusted-device-sse-failures-classified-by-sub-reason","canonical_anchor":"untrusted-device-sse-failures-classified-by-sub-reason","heading":"Clearer reasons when a remote session refuses an untrusted device","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/untrusted-device-sse-failures-classified-by-sub-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Clearer reasons when a remote session refuses an untrusted device\n\nFailed remote session connections for untrusted devices now carry a specific reason, with unknown ones reported as remote_connect_unknown_sub_reason\n\n**Unclear.** It is not clear whether these reasons are shown to the user or only recorded for diagnostics.\n\n**What**\n\nWhen Claude Code fails to open the live connection to a remote session, it now reads a reason and extra detail sent with the failure, instead of only checking for a plain \"untrusted device\" message. If the untrusted-device reason is one Claude Code does not recognise, it is reported as `remote_connect_unknown_sub_reason`.\n\n**Why**\n\nThis gives more specific diagnostics when a remote connection is refused because the device is not trusted.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}