{"version":"2.1.224","anchor":"bridge-close-codes-distinguish-auth-failure-from-recoverable","canonical_anchor":"bridge-close-codes-distinguish-auth-failure-from-recoverable","heading":"Bridge close codes distinguish auth failure from recoverable stalls","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/bridge-close-codes-distinguish-auth-failure-from-recoverable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Bridge close codes distinguish auth failure from recoverable stalls\n\nRemote bridge disconnects now use distinct close codes for session problems versus expired tokens.\n\n**What**\n\nWhen the remote-control connection hits a terminal request-path condition, the close code now reflects the cause: session or epoch problems close with 4090, expired or exhausted tokens with 4094.\n\n**Details**\n\n- Both places that build the client opt into typed close codes, so the mapping is what runs; the untyped path still closes with 4090 for everything.\n\n**Evidence**\n\n`terminal request-path condition`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}