[BUG] Same windows OAUTH issue from yesterday

Open 💬 17 comments Opened Apr 7, 2026 by scottgriffinm

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?

Same as what was happening yesterday before the fix, auth via claude /login on my Windows 11 ARM machine always results in OAuth error: Request failed with status code 500 or a timeout.

Very sad to have this happen again today

What Should Happen?

Successful authentication

Error Messages/Logs

OAuth error: Request failed with status code 500

Steps to Reproduce

  1. Install latest version of claude code on windows 11
  2. claude /login
  3. Follow steps, you will get OAuth error: Request failed with status code 500 or a timeout

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.92 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

17 Comments

lizhi317 · 3 months ago

me too

<img width="407" height="532" alt="Image" src="https://github.com/user-attachments/assets/53c7df33-1293-490e-b523-3f9638b94d07" />

dmki · 3 months ago

Same thing. And not only it's unable to authenticate, but also is wasting money in process. Version 2.1.90 is affected too.

larryb-swyfft · 3 months ago

day 2 of not being able to use claude.

xrompdev · 3 months ago

+1

github-actions[bot] · 3 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/44289
  2. https://github.com/anthropics/claude-code/issues/44286
  3. https://github.com/anthropics/claude-code/issues/44259

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

jakub-digital · 3 months ago

<img width="580" height="229" alt="Image" src="https://github.com/user-attachments/assets/881b0782-80a2-4c38-804d-4e026628d025" />

on web but 500 on CC

<img width="385" height="96" alt="Image" src="https://github.com/user-attachments/assets/829c5c71-599a-4530-9037-4c10d1f00957" />

ftab · 3 months ago

Same error. Tried restarting IDE. Tried restarting browser. Tried restarting computer. Tried different browser.

Sort your shit, Claude, for realsies. I don't know why I have to log in 4x a day when your login stuff never works.

kyleeruth · 3 months ago

also having the login issue as I did yesterday.

<img width="322" height="76" alt="Image" src="https://github.com/user-attachments/assets/0c6977bb-e074-4fb4-b3f3-7d09d1e67112" />

AlainPilon · 3 months ago

Same.

606scat · 3 months ago

+1

AbbasShDev · 3 months ago

Same issue

<img width="696" height="419" alt="Image" src="https://github.com/user-attachments/assets/2e21b8b2-278f-4b2d-a3a8-aed1c6abc22e" />

jakub-digital · 3 months ago
jackson97workflow-design · 3 months ago

hell na y'all this going to collapse the economy one day mark my words

benlinton · 3 months ago

+1

dmki · 3 months ago

It also appears that sometimes website is generating the code (which won't work, claude code will display error 500) or is telling "you can now close this window" a second after the client times out. So either it's a problem with timeout or, more likely, the new vibe-coded authentication backend fails after Anthropic patched it after the source code leaked. Let me guess - it requires the new unreleased client?

P.S. The existing authenticated clients are unaffected, so it is, apparently, the new token generation that fails. I wonder if token renewal is failing too, we are about to find out.

elliottlawson · 3 months ago

Same issues as yesterday. My existing connections were de-authed and no re-auth method is working.

notitatall · 3 months ago

Apologies for the disruption, folks! We believe this issue has been resolved.