{"version":"2.1.312","anchor":"oauth-token-revoke-stricter-acknowledgement-and-token-hint","canonical_anchor":"oauth-token-revoke-stricter-acknowledgement-and-token-hint","heading":"Logging out is only confirmed when Anthropic's server really answered","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/oauth-token-revoke-stricter-acknowledgement-and-token-hint","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Logging out is only confirmed when Anthropic's server really answered\n\nA token cancellation at logout is no longer counted as confirmed when the success reply lacks an Anthropic request id\n\n**What**\n\nWhen you log out, Claude Code asks Anthropic's server to revoke your sign-in token, meaning to cancel it so it can no longer be used. Before, any success reply counted as confirmation. Now a success reply that carries no Anthropic request id is not counted. Claude Code logs the message \"OAuth token revoke answered 2xx without an Anthropic request id; not counted as acknowledged.\" instead.\n\nThe cancel request can also say which kind of token it is cancelling, and defaults to the refresh token as before. It now sends Claude Code's shared extra network options, and so does the request that creates an API key.\n\n**Why**\n\nIf you are behind a proxy, which is a go-between server that relays your traffic, the proxy may answer \"success\" itself without ever reaching Anthropic. Such a reply no longer counts as your token having been cancelled on the server.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}