{"version":"2.1.222","anchor":"dedicated-error-when-claude-ai-rejects-a-session-bearer-toke","canonical_anchor":"dedicated-error-when-claude-ai-rejects-a-session-bearer-toke","heading":"Dedicated error when claude.ai rejects a session bearer token","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/dedicated-error-when-claude-ai-rejects-a-session-bearer-toke","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Dedicated error when claude.ai rejects a session bearer token\n\nIf claude.ai rejects your session token, you now get a clear message telling you to run \/login instead of endless retries.\n\n**What**\n\nMCP connections proxied through the claude.ai connector now surface a specific error telling you to re-login, instead of a generic auth failure that gets retried.\n\n**Details**\n\n- New `ClaudeAiProxyBearerRejectedError` class with code `CLAUDEAI_BEARER_REJECTED`.\n- Message: \"claude.ai rejected the session token \u2014 it may lack connector scopes or be invalid. Run \/login.\"\n- Two retry classifiers return false for it, so it is neither retried nor treated as a generic auth failure.\n- Added to the known-error name allowlists, alongside `McpAuthError` and `McpError`.\n- Connection failures report `errorCode: \"CLAUDEAI_BEARER_REJECTED\"` on `tengu_mcp_server_connection_failed`.\n\n**Evidence**\n\n`CLAUDEAI_BEARER_REJECTED`\n\n- Area: MCP\n- Names: `\/login`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}