{"version":"2.1.290","anchor":"bridge-no-longer-reports-transient-or-epoch-conflict-callba","canonical_anchor":"bridge-no-longer-reports-transient-or-epoch-conflict-callba","heading":"Simpler handling of refused remote-session token requests","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/bridge-no-longer-reports-transient-or-epoch-conflict-callba","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Simpler handling of refused remote-session token requests\n\nA remote session's worker-token request now treats every conflict as a plain refusal with no separate temporary-failure path\n\n**Unclear.** What this does to reconnecting in practice is not clear.\n\n**What**\n\nRemote sessions ask a bridge service for a worker token, a short-lived credential. Claude Code used to handle that request's failures in several separate ways. It now does less:\n\n- There is no separate path for temporary failures.\n\n- It no longer tells apart the kinds of conflict the server reports.\n\n- A conflict reply is now treated as a refusal, along with the newer session counter the server sent back.\n\n- The expected counter is sent whenever request options are given.\n\n**Why**\n\nThe logic for reconnecting a remote session is simpler.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}