{"version":"2.1.311","anchor":"sessions-api-401-on-teleportoauth-now-triggers-a-background","canonical_anchor":"sessions-api-401-on-teleportoauth-now-triggers-a-background","heading":"Background requests that fail sign-in now trigger a follow-up call","tier":"internal","area":"Login","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/sessions-api-401-on-teleportoauth-now-triggers-a-background","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Background requests that fail sign-in now trigger a follow-up call\n\nWhen a background or retried request using your stored sign-in token is refused as unauthorized, Claude Code now makes a follow-up call about that token\n\n**What**\n\nClaude Code sends requests to its sessions service using a sign-in token kept in your keychain, your system's secure password store. Recovery after a 401, an answer meaning the request was not authorized, used to run only for requests made in the foreground. When a background or retried request that used the stored token gets a 401, Claude Code now starts a follow-up call about that token in the background.\n\n**Why**\n\nThis may make sign-in recovery more reliable for requests that run in the background.\n\n- Area: Login\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}