[BUG] Auth Flow Broken (Windows)
Status Open
Reported on v2.1.92
Maintainer reply None cached
Activity 13 comments · opened Apr 6, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
I'm using a windows machine, and I was kicked out of CC on desktop and in terminal.
When trying to log back in, this error is being through:
Please run /login · API Error: 401
What Should Happen?
A user should log in
Error Messages/Logs
/login
⎿ Login interrupted
> test
⎿ Please run /login · API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"Invalid authentication credentials"},"request_id":"req_011CZnkcec8x3wbna5YnkUn1"}Steps to Reproduce
- /login
- click the link
- log in
- Watch
Claude Model
Not sure / Multiple models
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.92
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Warp
Additional Information
_No response_
13 Comments
+1
I’m also affected by this issue.
Claude Code on Windows (v2.1.92) fails to log in with Google and keeps showing:
OAuth error: timeout of 15000ms exceededI’ve tried multiple times and I’m still locked out, so I cannot use Claude Code at all. This appears to be the same problem described in this issue. Please prioritize a fix.
Same here, but I'm on MacOS.
same
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
also affecting me on mac, trying to auth in VScode extension on a mac. Web sessions still work
+1
+1, also getting
OAuth error: timeout of 15000ms exceededLogging in with Claude.ai Subscription causes multiple errors.
Also on Linux, same result trying to auth from Claude Code with other (older) versions
Same here on mac and linux
Hi friends! Sorry for the trouble and thank you for your reports. We're are working on this issue now. You can follow along here
Worked fine yesterday evening and this morning, now failing again with the same symptoms. Obviously related to peak use during the 15-17h UTC window.