You'll notice
Useful3 Signal0
Fixes MCP re-authentication misfiring by reading the real HTTP status instead of guessing from messages.
What's wrong with this entry?
Anonymous. No account, no email.
What
MCP auth-challenge classification is now driven by the HTTP error's status property rather than its code field.
Details
- Auth-challenge classification for sse/http/claudeai-proxy connect failures and the ENDPOINT_NOT_FOUND special case prefer
.status, falling back to.code. - The claudeai-proxy 401/403 re-auth path does the same.
- The GET-stream 404 check no longer matches on the message text.
Evidence
get_stream_404_not_reinit
Strings lifted out of the shipped bundle, so the claim above can be checked against them.