Live data from Hacker News

Claude Code login fails with OAuth timeout on Windows

github.com

31–40 of 331 posts

Re: Claude Code login fails with OAuth timeout on Windows

#31

Earlier quoted context omitted.

And they are early adopters of the vibe coding paradigm, having a 100% Claude generated codebase.

I assume most of their outages is related to this insane scaling and lack of available compute. Vibe coding doesn't automatically mean lower quality. My codebase quality and overall app experience has improved since I started using agents to code. You can leverage AI to test as well as write new code.

    > I assume most of their outages is related to this insane scaling and lack of available compute.
    > 
    > Vibe coding doesn't automatically mean lower quality
Scalability is a factor of smart/practical architectural decisions. Scalability doesn't happen for free and isn't emergent (the exact opposite is true) unless it is explicitly designed for. Problem is that ceding more of the decision making to the agent means that there's less intentionality in the design and likely a contributor to scaling pains.

Re: Claude Code login fails with OAuth timeout on Windows

#33

The solution is clearly more vibe coding at anthropic. I doubt even the core engineers know how to begin debugging that spaghetti code.

correct proompt is:"you are a senior engineer. fix issues. NO hallucinations this time. PRETTY PLEASE"

Re: Claude Code login fails with OAuth timeout on Windows

#35
post #24

Earlier quoted context omitted.

I assume most of their outages is related to this insane scaling and lack of available compute. Vibe coding doesn't automatically mean lower quality. My codebase quality and overall app experience has improved since I started using agents to code. You can leverage AI to test as well as write new code.

Isn't the whole selling point of AI agents that you now can do things like scale 3x without scaling your team accordingly?

I assume so. They're doing it with around 99% uptime.

Re: Claude Code login fails with OAuth timeout on Windows

#37
post #21

Not sure how Claude and CC has become the defacto best model given gpt 5.3 codex and 5.4 exist. This space moves so fast you should be testing your workflows on different models at least once every quarter, prudently once a month.

Checking different models once every quarter is exactly what made me move to claude code.

Re: Claude Code login fails with OAuth timeout on Windows

#38
post #8

Mounting evidence that claude max users are put into one big compute fuel pool. Demand increased dramatically with OpenAI's DoD PR snafu (even though Anth was already working with the DoD? But I digress...). The pool hit a ceiling. Anth has no compute left to give. Hence people maxing out after 1 query. "Working on it" means finding a way to distill Claude Code that isn't enough of a quality degradation to be noticed…

Makes sense, even plan name seems to agree: "Claude Max".

Re: Claude Code login fails with OAuth timeout on Windows

#39

Earlier quoted context omitted.

I assume most of their outages is related to this insane scaling and lack of available compute. Vibe coding doesn't automatically mean lower quality. My codebase quality and overall app experience has improved since I started using agents to code. You can leverage AI to test as well as write new code.

After the CC leak last week I took a look at their codebase and my biggest criticism is they seem to never do refactoring passes. Personally I write something like 80-90% of my code with agents now but after they finish up, it's critical that you spin up another agent to clean up the code that the first one wrote. Looking at their code it's clear they do not do this (or do this enough). Like the main file being somet…

How do you do the cleanup? Just /simplify or something you rolled yourself?

Re: Claude Code login fails with OAuth timeout on Windows

#40
post #24

Earlier quoted context omitted.

I assume most of their outages is related to this insane scaling and lack of available compute. Vibe coding doesn't automatically mean lower quality. My codebase quality and overall app experience has improved since I started using agents to code. You can leverage AI to test as well as write new code.

Isn't the whole selling point of AI agents that you now can do things like scale 3x without scaling your team accordingly?

I haven't seen anyone claim that applies to infrastructure or compute.
Post reply on HN