{"version":"2.1.277","anchor":"ccr-auth-token-refresh-now-accepts-gateway-placeholder-ses","canonical_anchor":"ccr-auth-token-refresh-now-accepts-gateway-placeholder-ses","heading":"CCR auth-token refresh now accepts 'gateway placeholder' session tokens, not just JWTs","tier":"internal","area":"CCR","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/ccr-auth-token-refresh-now-accepts-gateway-placeholder-ses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### CCR auth-token refresh now accepts 'gateway placeholder' session tokens, not just JWTs\n\nCCR auth-token refresh now also accepts a non-JWT 'gateway placeholder' session token\n\n**What**\n\nWhen Claude Code Remote refreshes its authentication token, the session token it receives can now be one of three things: a decodable JWT (checked as before for expiry and staleness), a non-JWT \"gateway placeholder\" token that must match either the token currently held in the process or a previously verified JWT, or a token that gets rejected outright. When a placeholder token is adopted, it's logged in the `cli_worker_auth_refresh_adopted` event with a new `session_token` field describing which of these cases matched.\n\n**Why**\n\nThis lets remote authentication refresh handle a wider range of valid session token formats without weakening the checks that reject tokens that don't match anything trusted.\n\n- Area: CCR\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}