{"version":"2.1.312","anchor":"bridge-pr-auth-refresh-fix-and-ticket-header-echo","canonical_anchor":"bridge-pr-auth-refresh-fix-and-ticket-header-echo","heading":"Fixed sign-in refresh handling for pull request calls in bridge sessions","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/bridge-pr-auth-refresh-fix-and-ticket-header-echo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Fixed sign-in refresh handling for pull request calls in bridge sessions\n\nPull request calls that fail with an authorization error now check the right response, and some requests echo ticket headers back\n\n**What**\n\nIn bridge sessions, where Claude Code is driven from another place such as a remote host, a pull request call that fails with a 401 error (meaning \"not authorized\") now checks the correct response. It also decides from the request's own authorization header whether to skip refreshing the sign-in.\n\nSeparately, some requests now send the `x-ccr-ticket-rev` header and its session and sequence companions back to the server.\n\n**Why**\n\nThe old check looked at the wrong response, so sign-in refreshes after a failed pull request call could go wrong.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}