🌐
GitHub
github.com › anthropics › claude-code › issues
anthropics/claude-code
October 31, 2025 - #15065 In anthropics/claude-code; · rridngs opened · on Dec 22, 2025 · bugSomething isn't workingSomething isn't working · has reproHas detailed reproduction stepsHas detailed reproduction steps · platform:windowsIssue specifically occurs on WindowsIssue specifically occurs on Windows ·
Author   anthropics
🌐
Claude
status.claude.com
Claude Status
Identified - Due to a bug introduced in Claude iOS app version 1.251117.1 (November 18), some Apple App Store users who purchased Pro and Max plans on or after November 24 did not receive proper access to their plans. The mobile purchasing bug has been resolved.
Discussions

Claude Opus solved my white whale bug today that I couldn't find in 4 years
"It wasn't technically working either where you thought it was working" bugs are the WORST. Congrats. And I for one welcome our new robot overlords. More on reddit.com
🌐 r/ClaudeAI
224
1938
May 25, 2025
Megathread for Claude Performance, Limits and Bugs Discussion - Starting September 28
I'm strongly considering not renewing my subscription again after this month if these are the actual limits and it's not some bug. I'm on the $20 plan, I stick mostly to Sonnet 3.7 and sometimes Sonnet 4, and use it for creative writing. When I first started using Claude in May the usage limits were great, I never hit any warnings, again, I use it for creative writing. Slowly those limits have gotten worse and worse. Today with the new usage meter I can see that with barely any use I'm already at 10% of my WEEKLY usage! How is that possible? I tried out Sonnet 4.5 -which honestly doesn't feel like much of an improvement compared to 3.7 or Sonnet 4 at least for my uses- for my first few prompts, then switched back to 3.7 and somehow I'm at 10% for the week? I realize I'm on the lowest paying subscription but at this point, if I'm going to be hitting weekly limits so easily, I'd rather switch back to using Openrouter and API's. I'm really hoping these new weekly limits are just buggy... More on reddit.com
🌐 r/ClaudeAI
224
16
September 29, 2025
I love Claude but the terminal scrolling bug is driving me insane : ClaudeAI
🌐 r/ClaudeAI
Claude code update bug : ClaudeAI
🌐 r/ClaudeAI
🌐
Anthropic
anthropic.com › engineering › a-postmortem-of-three-recent-issues
A postmortem of three recent issues
Illustrative timeline of events on the Claude API. Yellow: issue detected, Red: degradation worsened, Green: fix deployed. The overlapping nature of these bugs made diagnosis particularly challenging. The first bug was introduced on August 5, affecting approximately 0.8% of requests made to Sonnet 4.
🌐
Chameth
chameth.com › finding-an-awkward-bug-with-claude-code
Finding an awkward bug with Claude Code · Chameth.com
June 30, 2025 - The lock it’s talking about is a RWMutex, which is specifically designed to allow many read-locks. Everything it’s pointing out are read locks, so they cannot block one another as it described. The response Claude has given sounds very confident, seems appropriately technical, but is in fact complete rubbish.
🌐
Claude
claude.ai › public › artifacts › 4cf1ef69-295e-4de5-95e9-4c1070d59690
Bug Reporting Dashboard
Loading · Bug Reporting Dashboard | Claude · Content is user-generated and unverified · Customize
🌐
TechCrunch
techcrunch.com › home › anthropic’s claude code tool had a bug that ‘bricked’ some systems
Anthropic's Claude Code tool had a bug that 'bricked' some systems | TechCrunch
March 6, 2025 - The problematic Claude Code auto-update commands changed the access permissions of certain critical system files. Permissions define which programs and users can read or modify files, or run certain apps.
🌐
Made With Love
madewithlove.com › blog › why-i-switched-from-bugbot-to-claude-for-code-reviews
Why I switched from BugBot to Claude for code reviews
November 4, 2025 - With this prompt, Claude focuses solely on critical issues and provides a concise summary of suggested changes. Combined with limiting it to a single review per pull request, it’s proven to be a valuable time-saver. I’ve found it especially effective in smaller teams, where it helps speed up approvals and catches bugs that might slip past human reviewers.
🌐
Claude
code.claude.com › docs › en › troubleshooting
Troubleshooting - Claude Code Docs
Use project conventions: Document ... · If you’re experiencing issues not covered here: Use the /bug command within Claude Code to report problems directly to Anthropic ·...
🌐
InfoQ
infoq.com › news › 2025 › 10 › anthropic-infrastructure-bugs
Anthropic Reveals Three Infrastructure Bugs behind Claude Performance Issues - InfoQ
October 3, 2025 - The problems our users reported were due to infrastructure bugs alone (...) Each bug produced different symptoms on different platforms at different rates. This created a confusing mix of reports that didn’t point to any single cause. The team described the three overlapping issues: a context window routing error that, at the worst impacted hour on August 31, affected 16% of Sonnet 4 requests; an output corruption caused by a misconfiguration to the Claude API TPU servers that triggered an error during token generation, affecting requests made to Opus 4.1 and Opus 4 on August 25-28 and requests to Sonnet 4 from August 25 to September 2; and finally, an approximate top-k XLA:TPU miscompilation due to a latent bug in the compiler that affected requests to Claude Haiku 3.5 for almost two weeks.
Find elsewhere
🌐
Reddit
reddit.com › r/claudeai › claude opus solved my white whale bug today that i couldn't find in 4 years
r/ClaudeAI on Reddit: Claude Opus solved my white whale bug today that I couldn't find in 4 years
May 25, 2025 -

Background: I'm a C++ dev with 30+ years experience, ex-FAANG Staff Engineer. I'm generally the person on the team that other developers come to after they struggled with a problem for a week, and I would solve it while they are standing in my office.

But today I was humbled by Claude Opus 4.

I gave it my white whale bug which arose from a re-architecting refactor that was done 4 years ago. The original refactor span around 60k lines of code and it fixed a whole slew of problems but it created a problem in an edge case when a particular shader was used in a particular way. It used to work, then we rearchitected and refactored, and it no longer worked.

I've been playing on and off trying to find it, and must have spent 200 hours on it over the last few years. It's one of those issues that are very annoying but not important enough to drop everything to investigate.

I worked with Claude Code running Opus for a couple of hours - I gave it access to the old code as well as the new code, and told it to go find out how this was broken in the refactor. And it found it. Turns out that the reason it worked in the old code was merely by coincidence of the old architecture, and when we changed the architecture that coincidence wasn't taken into account. So this wasn't merely an introduced logic bug, it found that the changed architecture design didn't accommodate this old edge case.

This took a total of around 30 prompts and one restart. I've also previously tried GPT 4.1, Gemini 2.5 and Claude 3.7 and neither of them could make any progress whatsoever. But Opus 4 finally found it.

🌐
Reddit
reddit.com › r/claudeai › megathread for claude performance, limits and bugs discussion - starting september 28
r/ClaudeAI on Reddit: Megathread for Claude Performance, Limits and Bugs Discussion - Starting September 28
September 29, 2025 -

Latest Performance and Bugs with Workarounds Report: https://www.reddit.com/r/ClaudeAI/wiki/latestworkaroundreport

Full record of past Megathreads and Reports : https://www.reddit.com/r/ClaudeAI/wiki/megathreads/

Why a Performance and Bugs Discussion Megathread?

This Megathread should make it easier for everyone to see what others are experiencing at any time by collecting all experiences. Most importantly, this will allow the subreddit to provide you a comprehensive periodic AI-generated summary report of all performance issues and experiences, maximally informative to everybody. See the previous period's performance and workarounds report here https://www.reddit.com/r/ClaudeAI/wiki/latestworkaroundreport

It will also free up space on the main feed to make more visible the interesting insights and constructions of those using Claude productively.

What Can I Post on this Megathread?

Use this thread to voice all your experiences (positive and negative) as well as observations regarding the current performance of Claude. This includes any discussion, questions, experiences and speculations of quota, limits, context window size, downtime, price, subscription issues, general gripes, why you are quitting, Anthropic's motives, and comparative performance with other competitors.

So What are the Rules For Contributing Here?

All the same as for the main feed (especially keep the discussion on the technology)

  • Give evidence of your performance issues and experiences wherever relevant. Include prompts and responses, platform you used, time it occurred. In other words, be helpful to others.

  • The AI performance analysis will ignore comments that don't appear credible to it or are too vague.

  • All other subreddit rules apply.

Do I Have to Post All Performance Issues Here and Not in the Main Feed?

Yes. This helps us track performance issues, workarounds and sentiment and keeps the feed free from event-related post floods.

Top answer
1 of 4
9
I'm strongly considering not renewing my subscription again after this month if these are the actual limits and it's not some bug. I'm on the $20 plan, I stick mostly to Sonnet 3.7 and sometimes Sonnet 4, and use it for creative writing. When I first started using Claude in May the usage limits were great, I never hit any warnings, again, I use it for creative writing. Slowly those limits have gotten worse and worse. Today with the new usage meter I can see that with barely any use I'm already at 10% of my WEEKLY usage! How is that possible? I tried out Sonnet 4.5 -which honestly doesn't feel like much of an improvement compared to 3.7 or Sonnet 4 at least for my uses- for my first few prompts, then switched back to 3.7 and somehow I'm at 10% for the week? I realize I'm on the lowest paying subscription but at this point, if I'm going to be hitting weekly limits so easily, I'd rather switch back to using Openrouter and API's. I'm really hoping these new weekly limits are just buggy...
2 of 4
7
Has anyone else been running up against the 5-hour limit consistently? If I remember correctly the 5-hour limit (when it was introduced) was billed as something that would impact a small minority of users - those in the top few percent - and meant as a deterrant for abusive and wasteful usage of the platform. Nevertheless, I'm running into this rate limit almost every session that goes more than a few hours as a Max $100 tier user. I'm someone who is not burning tokens with poor context building or reckless vibes-only coding. I'm reviewing all of Claude's outputs and manually accepting changes most if not all of the time. I also don't have hours on end available across the day to wait for the wondow to reset. When I have a few hours to code, that's all I'll have until later in the week or even the next week. On average, I spend maybe 15 hours a week working with Claude. It seems to me the 5-hour limit was hastily conceived, poorly thought out, and isn't even achieving the ends it was created to achieve. Does anyone else have the same experience?
🌐
Overreacted
overreacted.io › how-to-fix-any-bug
How to Fix Any Bug — overreacted
October 21, 2025 - The problem is that “scrolling jitters” from my repro didn’t mean anything to Claude. Claude doesn’t have eyes or other ways to perceive the jitter directly. So Claude was essentially operating without a repro—it tried to fix the bug, but didn’t do anything specific to verify it.
🌐
Bloombergtechnoz
bloombergtechnoz.com › teknologi › teknologi
Model AI Baru Milik Anthropic Bisa Secara Otomatis Perbaiki Bug - Teknologi
1 month ago - Claude Opus 4.5 digadang-gadang lebih canggih dari versi sebelumnya khususnya dalam pekerjaan rekayasa perangkat lunak, seperti memperbaiki bug, tanpa memerlukan bantuan pengguna, kata Anthropic.
🌐
Claude
claude.com › fix software bugs faster with claude
Fix software bugs faster with Claude | Claude
November 21, 2025 - Claude identifies patterns in error data, highlighting the specific service, configuration change, or code path that's responsible. Instead of "investigate API failures," your team gets "check rate limiting in auth service."
🌐
36Kr
eu.36kr.com › en › p › 3437724194934153
Musk's Pal Karpathy Issues New Guide: GPT - 5 Pro Is AI Programming's Last Line of Defense
August 24, 2025 - For example, to locate a specific bug, Claude Code can write 1000 lines of one-time, extremely detailed visualization code in one go.
🌐
Gaoxiaoma
xugj520.cn › home › best ai development tools for 2025: 7 tested tools that boost productivity
Best AI Development Tools for 2025: 7 Tested Tools That Boost Productivity | Efficient Coder
August 28, 2025 - # Python example import anthropic client = anthropic.Anthropic( api_key="your_api_key" ) response = client.messages.create( model="claude-3-opus-20240229", max_tokens=1000, messages=[ {"role": "user", "content": "Explain this code snippet..."} ] ) print(response.content)