When your claude.ai session token is rejected, you now get a clear error telling you to run /login.
What's wrong with this entry?
A 401 from the claude.ai proxy that a token refresh cannot fix now becomes a typed error telling you to run /login, instead of silently returning the original failed response.
- error code CLAUDEAI_BEARER_REJECTED, recognised by connect, tools/list, prompts/get and skills/list
- sets
discoveryBearerRejectedon the client and skips the usual "degraded" telemetry - emits mcp_connect_claudeai_bearer_rejected and mcp_reconnect_bearer_rejected
- the failed entry is evicted from the connection cache so a later attempt retries
claude.ai rejected the session token — it may lack connector scopes or be invalid. Run /login.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
Remote Control tells you when a credential expired instead of just dropping
Both mention login
-
v2.1.224
Remote Control errors are typed as auth or terminal
Both mention login
-
v2.1.225
Remote Control re-arms itself after a re-login
Both mention login