Claude Code error
Claude Code: OAuth error: timeout of 15000ms exceeded
OAuth error: timeout of 15000ms exceededStatus: OpenLast verified 3 documented fixes3 sources
What it means
The /login or claude auth login flow failed at the final step after browser authorization, timing out waiting for the server.
Causes
- A service-side incident: on #33213 an Anthropic team member assigned to the issue wrote "Apologies for the disruption, folks! We believe this issue has been resolved." linking a status.claude.com incident (2026-04-07). Users continued reporting it afterward and the issue remains open.
How to fix it
- Fix 1.
Check status.claude.com for an active incident; the maintainer response on #33213 tied the April 2026 occurrence to a resolved incident.
- Fix 2.
Official generic login reset: run /logout, close Claude Code, restart with claude and complete authentication again. If the browser does not open, press c to copy the OAuth URL.
Slash command/logout - Fix 3.
In WSL2, SSH, or containers, paste the login code shown in the browser at the Paste code here if prompted prompt, or use claude auth login, which reads the pasted code from standard input.
Terminalclaude auth login
More Claude Code errors
All 18 Claude Code errorsAPI Error: 500 Internal server error. This is a server-side issue, usually temporaryStatus: WorkaroundAPI Error: Repeated 529 Overloaded errors. The API is at capacityStatus: WorkaroundAPI Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"messages.5: `tool_use` ids were found without `tool_result` blocks immediately after: toolu_01FRvEykWmCgrgJ22mvBbKhV. Each `tool_use` block must have a corresponding `tool_result` block in the next message."}}Status: OpenUnable to connect to API. Check your internet connectionStatus: WorkaroundUnable to connect to API: SSL certificate verification failed (UNABLE_TO_GET_ISSUER_CERT_LOCALLY).Status: WorkaroundPlease run /login · API Error: 401 OAuth token has expiredStatus: WorkaroundPrompt is too longStatus: WorkaroundYou've hit your session limit · resets 3:45pmStatus: By design
Related reading
- Claude Code Idle Compaction: What It Does and How to Turn It OffClaude Code 2.1.299 compacts sessions over 200K tokens after about 54 idle minutes. How the cache math works, the setting to turn it off, and when to keep it.
- Claude Code Desktop SneakPeek Flaw: Fixed Version and What To DoSneakPeek (CVSS 8.7) let a poisoned HTML file read SSH keys and cloud credentials via the Claude Code Desktop preview pane. Fixed in Claude Desktop 1.30096.1.
- Reverse Engineer Anything (REA): What the MCP Server Does and Where the Line IsREA (Reverse Engineer Anything) is an MIT-licensed MCP server that lets Claude Code, Codex or Cursor inspect binaries, Electron apps and APKs. How to try it.
- Claude Code Projects: Coordinator, Threads, and LimitsClaude Code Projects is open to waitlisted Pro and Max users. How the coordinator and cloud threads work, what they cost in plan limits and where it breaks.
- Agent Harness Lessons From a 500B-Token Decompile: Give Agents a PASS/FAIL OracleAgent harness lessons from a 500B+ token decompile: a byte-matching PASS/FAIL oracle beat the reviewer agent. How agents cheated it and what to copy.
- Claude for Startups Offer Paused: What Founders Do NowClaude for Startups paused its free Claude Team year and $1,000 API credit offer at capacity. What the program page says now and how to cover the gap.
FAQ
What does "OAuth error: timeout of 15000ms exceeded" mean in Claude Code?
The /login or claude auth login flow failed at the final step after browser authorization, timing out waiting for the server.
How do I fix "OAuth error: timeout of 15000ms exceeded"?
There are 3 documented fixes. Start with the first: Check status.claude.com for an active incident; the maintainer response on #33213 tied the April 2026 occurrence to a resolved incident.
Is this Claude Code error fixed?
Status: Open. Still open upstream. Any documented fixes are workarounds so far. Affected versions: Reported on 2.1.72 through 2.1.109 and later in #33213.
Sources
Last verified against 3 sources: official docs, maintainer replies and release notes.
Newsletter
Fixes for the tools you use, weekly
One email per week. New coding agent releases, what broke, and how developers are working around it.