Claude Code outage locks users out for hours with Google OAuth timeouts

What happened

It has been reported that users of Claude Code were suddenly unable to sign in after Google OAuth flows timed out, effectively locking them out of the app for hours. The problem was logged in a high-traffic GitHub issue (anthropics/claude-code#44257) where frustrated users described repeated OAuth failures that prevented access across multiple machines. The company’s status page was updated to reflect a partial outage, and the error messages read like a bad punchline: login required, login failed, timeout — rinse and repeat.

Who was affected

Windows users were hit hard — Windows 11, WSL2, PowerShell — but macOS users also reported the same timeout behavior. It has been reported that the outage impacted other surfaces like Claude.code, not just the desktop app. One commenter said the service returned after about 5.5 hours; another said updating from 2.1.91 to 2.1.92 cleared the problem on their machines. Meanwhile, some forum speculation — allegedly tied to the team’s internal changes, like disabling “Clawed” — circulated among users, but that claim has not been confirmed.

Why it matters (and what’s next)

This was more than an annoying bug. For people mid-flow, it was work stopped cold — blocked from their tools by a timeout. The Claude team reportedly told users they read every piece of feedback; now the focus will be on preventing single sign-on hiccups from becoming full-on lockouts. So: will the fix be a quick patch, a version rollout, or a deeper infrastructure change? Time will tell — and users will be watching the status page.

Sources: github.com/anthropics, Hacker News