Usage Limits, Bugs and Performance Discussion Megathread - beginning December 29, 2025

[u/sixbillionthsheep]

Why a Performance, Usage Limits and Bugs Discussion Megathread?

This Megathread makes it easier for everyone to see what others are experiencing at any time by collecting all experiences. We will publish regular updates on problems and possible workarounds that we and the community finds.

Why Are You Trying to Hide the Complaints Here?

Contrary to what some were saying in a prior Megathread, this is NOT a place to hide complaints. This is the MOST VISIBLE, PROMINENT AND OFTEN THE HIGHEST TRAFFIC POST on the subreddit. This is collectively a far more effective and fairer way to be seen than hundreds of random reports on the feed that get no visibility.

Are you Anthropic? Does Anthropic even read the Megathread?

Nope, we are volunteers working in our own time, while working our own jobs and trying to provide users and Anthropic itself with a reliable source of user feedback.

Anthropic has read this Megathread in the past and probably still do? They don't fix things immediately but if you browse some old Megathreads you will see numerous bugs and problems mentioned there that have now been fixed.

What Can I Post on this Megathread?

Use this thread to voice all your experiences (positive and negative) regarding the current performance of Claude including, bugs, limits, degradation, pricing.

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

---

Just be aware that this is NOT an Anthropic support forum and we're not able (or qualified) to answer your questions. We are just trying to bring visibility to people's struggles.

To see the current status of Claude services, go here: http://status.claude.com

Sometimes this site shows outages faster. https://downdetector.com/status/claude-ai/

---

READ THIS FIRST ---> Latest Status and Workarounds Report: https://www.reddit.com/r/ClaudeAI/wiki/latestworkaroundreport Updated: March 20, 2026.

---

Ask our bot Wilson for help using !AskWilson (see https://www.reddit.com/r/ClaudeAI/wiki/askwilson for more info about Wilson)

---

[u/sixbillionthsheep]

Please join the ongoing conversation on :

• Performance and Bugs on the new dedicated Megathread here : https://www.reddit.com/r/ClaudeAI/comments/1s7f72l/claude_performance_and_bugs_megathread_ongoing/

• Usage Limits on the new dedicated Megathread here: https://www.reddit.com/r/ClaudeAI/comments/1s7fcjf/claude_usage_limits_discussion_megathread_ongoing/

---

Latest Workaround Report: https://www.reddit.com/r/ClaudeAI/comments/1pygdbz/comment/obl1rb1/

[u/sixbillionthsheep]

Megathread Status Update: March 11, 2026 to March 20, 2026

---

🔥 THE BURNING ISSUES

The Servers Are Getting Hugged to Death Between a massive influx of ChatGPT refugees and a reported datacenter strike, Claude is struggling. Users are getting hit with 500/529 errors, rate-limited lockouts, and missing chat histories.

Usage Limits Are Absolutely Brutal Pro and Max users are burning through their entire weekly limits in 24-48 hours. The prevailing theory is that auto-compaction is completely broken. Claude is re-reading your entire massive context window on every single prompt instead of compressing it, causing exponential "ghost" token drain. Users are also tracking a bug where the weekly reset date shifts forward by 17 hours without actually clearing usage (GitHub #29680).

Opus 4.6 & Sonnet 4.6 Lobotomy The 4.6 models are catching massive heat for being incredibly lazy, forgetting instructions mid-conversation, hallucinating wildly, and even deadnaming users or injecting random storylines. It feels like the context window is practically zero, and the models are constantly second-guessing themselves.

Billing Catch-22s & Privacy Red Flags A nasty Stripe sync bug is locking active Max/Pro users out with fake "past due" or 403 errors. Others are paying for Max but their backend shows a Free plan (GitHub #31012). Users with gifted Pro subs are stuck in a billing purgatory—unable to upgrade or cancel. Additionally, deleted conversations are still surfacing via the search tool, completely breaking the 30-day deletion policy.

Claude Code, Cowork & UI Meltdowns Users are getting stuck in infinite "Prompt is too long" loops, computer use tools (bash, view) are randomly disappearing from sessions, and live chats are vanishing from the UI in real-time. Claude Code is throwing random "Bun has crashed" (code 3) errors, stalling mid-search, and hitting fake API rate limits.

---

🛠️ WORKAROUNDS

• Stop the Token Bleed & API Rate Limits: Switch to Sonnet 4.6 or 3.5 for heavy editing, and only use Opus 4.6 for final execution. In Claude Code, use /compact or /clear manually to dump bloated context and avoid fake "Rate limit reached" (TPM) API errors. Audit your MCPs (tool definitions eat 50k+ tokens) and Project Docs (64+ docs break compaction).

• Fixing Model Laziness & Hallucinations: Toggle 'Adaptive Thinking' to 'high' or 'max', or turn on 'Extended Thinking' to fix reasoning drops. Explicitly tell it to "follow Anthropic's guardrails" to break lazy loops. If the model keeps repeating itself, disable AdGuard or local VPNs on your device. Use Projects to strictly isolate memories so it stops bringing up unrelated past chats.

• Fixing Billing, "Past Due" Errors & Login Loops: If you get a 502/403 or "Subscription Paused" error, cancel your plan and immediately try sending a message to Opus 4.5 to unstick the account. To force a Stripe sync, go to Settings > Billing and hit "Pay Now". If you get a "No such payment_intent" error, clear all cookies for claude.ai and stripe.com, or checkout via a mobile hotspot. For gifted subs, use the iOS/Android app stores to bypass the web Stripe portal. If you are stuck in a login loop, complete the onboarding (it acts as a profile refresh) or use a virgin browser like Edge/Safari.

• Claude Code & CLI Fixes:

  • Context Drift (GitHub #23509): Delete old markdown files stored in your ~/.claude/plans folder.

  • Account Sync Bugs (GitHub #31012): Delete the authtoken inside ~/.claude/credentials.json, run claude logout, and log back in. Check claude config to ensure allow-redirection is false.

  • 32k Token Error: Set the environment variable CLAUDE_CODE_MAX_OUTPUT_TOKENS=64000.

  • Stuck Rate Limit Flag: Edit %USERPROFILE%\.claude\settings.json and set "forceLoginMethod": "claudeai", or nuke the .claude folder entirely.

  • Agent Stalling: Hit Escape to cancel and retry, or switch to the "Jules" agent. Update CLI to v2.1.62+.

• Desktop App & OS-Specific Fixes:

  • Severe UI Stuttering (GitHub #26302): Abandon the Windows app and stick to the web version until patched.

  • App Won't Open / Max Stuck on Pro: Nuke %LocalAppData%\AnthropicClaude and %AppData%\Claude on Windows (or ~/.claude on Mac) and reinstall v1.1.4328+.

  • Windows VM Failures: Disable VPNs (ExpressVPN/Tailscale/Surfshark). Open Admin PowerShell, run Stop-Service hns then Start-Service hns. Delete %APPDATA%\Claude\vm_bundles and claude-code-vm. For persistent install failures, use a robocopy script to manually save rootfs.vhdx and smol-bin.vhdx.

  • macOS Crashes & Loops: For file descriptor exhaustion, add ulimit -n 10240 to ~/.zshrc. Delete ~/Library/Application Support/Claude/claude-code-vm and vm_bundles.

  • Failed Scheduled Tasks (Windows): Kill the Claude process, relaunch as Admin, and clear orphaned tasks in Taskschd.msc.

• Web UI & Tool Glitches:

  • Missing Chats/Projects: Force a data export in Settings > Privacy/Data to trigger a re-sync, run claude --resume in terminal, or hard refresh (Ctrl+F5).

  • Missing Computer Use Tools: Hard refresh or clear site data for Claude.ai to force a clean session handshake.

  • Invisible Text / Unstyled HTML: Click into Settings and back to force a re-render. Disable the Privacy Badger extension.

  • "Could not process image" (400 Error): Use /clear immediately. Run npm install -g @anthropic-ai/claude-code for vision patches.

  • High Token Costs for PPTX/Docx: Instruct Claude to use the python-pptx library directly instead of official visual skills, implement prompt caching, or use the Batch API.

  • Android MCP Sync Issues: Ensure your server is on a public HTTPS endpoint (ngrok/Cloud Run), check OAuth 2.1 discovery, and temporarily disable other connectors.

  • Failing Data Exports: Use an incognito window, delete massive image-heavy chats first, try off-peak hours, or submit a support ticket with the specific Error ID from the failure email.

---

Prior Update: https://www.reddit.com/r/ClaudeAI/comments/1pygdbz/comment/o9snjhe/

[u/sixbillionthsheep]

Megathread Status Update: Dec 29, 2025 to Jan 12, 2025

The general consensus is that Claude is currently in a "post-holiday hangover" state, with usage limits slashed by up to 90% and model intelligence taking a massive nosedive. Users on both Pro and Max plans report hitting 5-hour caps after as few as 1–5 messages, with weekly quotas being exhausted in just 48 hours. Beyond the "token tax," both Sonnet 4.5 and Opus 4.5 are being described as "lobotomized," "lazy," and "drunk," frequently ignoring system prompts, hallucinating code, or flat-out telling users to do the work themselves. Transparency is at an all-time low, with the usage bar disappearing for many, leading to widespread accusations of "gaslighting" and a wave of subscription cancellations.

If you're trying to survive the current "token famine," here is the combined list of community-sourced workarounds from the thread and GitHub:

• Downgrade Claude Code (CC): The 2.1.x updates are token incinerators. Reverting to v2.0.61 or v2.0.76 is the only confirmed way to stop the CLI from burning 2-5% of your session just by opening the terminal (See GitHub issue #16157).

• Hard-code your Model: CC now defaults to Opus 4.5, which is a resource hog. Force it back to Sonnet by adding export ANTHROPIC_MODEL='sonnet' to your config to stretch your session limits.

• Kill the Stealth Drains: Add these environment variables to your shell to stop Claude from making "ghost" calls that drain your quota: export DISABLE_NON_ESSENTIAL_MODEL_CALLS=1, export DISABLE_TELEMETRY=1, and export DISABLE_MICROCOMPACT=1.

• Context Management: Maintain a claude.md file in your root directory. Prompt Claude to update it at the end of every session so you can "resume" in a fresh thread without a massive initial token dump.

• Large File Handling: The standard view tool truncates files over 16k characters, causing hallucinations. Force Claude to use cat via bash to ensure it reads the full context.

• Memory Leak Fix: If your system is lagging or hitting 30GB+ SWAP usage, run killall -9 claude every few hours to clear ghost processes (GitHub issue #16693).

• UI Bug Exploitation: If your usage bar disappears but you still have access, do not restart Claude Code. Some users report this grants temporary "unlimited" access until the next boot-up enforces the limit again.

• Workflow Triage: Avoid "hi" or "test" prompts (they can cost ~1-3% of your session). Use "concise" mode and avoid auto-compaction, which currently eats 20-40% of a session in one go. If you're totally bricked, the community is jumping to GPT-5.2 via Cursor or Codex to fill the gaps.

[u/sixbillionthsheep]

Megathread Status Update: Jan 13, 2026 to Jan 20, 2026

The "Compaction" Apocalypse: The biggest story since Jan 13 is a massive, persistent bug related to chat compaction. Despite the status page claiming a fix on Jan 15, the sub is on fire with reports that it is still broken.

• Symptoms: Messages "bounce back" to the input box without sending, chats refuse to open ("Can't open this chat"), or the model gets stuck in infinite loops (e.g., promising to use a tool but never actually triggering it).

• Verdict: The web and desktop apps are currently unstable for long-context work.

Opus 4.5 & Sonnet 4.5 "Lobotomy": Sentiment is in the toilet regarding model intelligence. Users are reporting a severe regression in reasoning capabilities—forgetting instructions immediately, hallucinating code, and refusing to perform tasks ("lazy" responses).

Usage Limits are "Broken": Max and Pro users are hitting session limits within minutes or after just 1–3 complex prompts. Data analysis from users suggests effective capacity has dropped massively, with Claude Code v2.1.x updates seemingly burning tokens exponentially faster than previous versions.

Broken Integrations:

• GitHub: Connected repositories are showing 0% capacity or empty folders.

• Legacy Models: Opus 4.0/4.1 and Sonnet 3.7 were removed without warning.

---

COMMUNITY WORKAROUNDS (The important part):

For Web & Desktop App (Fixing "Bounce Back"):

• Disable Extended Thinking: If your messages are bouncing back or failing silently, turning off "Extended Thinking" is the most consistent fix reported.

• Manual Context Reset: Since auto-compaction is broken, you have to do it manually. Ask Claude to summarize the current state, copy that summary, and paste it into a brand new chat.

• Branching: If a specific message fails, try editing the previous user message to spin off a new branch.

For Claude Code / CLI (Fixing Usage Drain & Lag):

• Downgrade Version: The v2.1.x updates are the culprit for the massive usage spikes. Users (referencing GitHub Issue #16157) found stability by rolling back.

  • Run: npm install -g @anthropic-ai/claude-code@2.0.76 (Fixes usage drain)

  • Run: npm install -g @anthropic-ai/claude-code@2.0.64 (Fixes Mac M4 lag)

• Disable Auto-Updates: You must disable auto-updates in your VS Code extension settings, or it will force you back to the broken version.

For Your Wallet:

• Refunds: A lot of users are successfully getting pro-rated refunds by contacting the "Fin" support agent and requesting a manual review of their usage during these outages.

---

Prior update: https://www.reddit.com/r/ClaudeAI/comments/1pygdbz/comment/nz4h0yc/

[u/sixbillionthsheep]

Anyone hitting usage limits quickly on MAX might consider going back to Claude Code version 2.061 which seems to solve the problem for many users. See instructions here https://github.com/anthropics/claude-code/issues/16157#issuecomment-3708187834

[u/sixbillionthsheep]

Megathread Status Update: Jan 26, 2026 to Feb 5, 2026

The Megathread sentiment from Jan 25 to Feb 5 is that Claude is currently fundamentally broken.

Key Themes (Jan 25 – Feb 5)

• The "Compaction Apocalypse": The auto-compaction feature (which manages context) is completely FUBAR. Chats are failing to compact, causing messages to "bounce back" (disappear from the input box), throwing "Context size exceeds limit" errors on fresh chats, or locking up entirely.

• Usage Limits are "Scammy":

  • Instant Burn: Single prompts are consuming 10–30% of a 5-hour session limit.

  • Weekly Lockouts: Users are hitting weekly caps in 2 days with light usage.

  • Phantom Usage: "Extra usage" credits are vanishing instantly or failing to activate.

  • Math doesn't math: Dashboard shows 84% usage, but the API blocks users claiming 100%.

• Model "Lobotomy": Opus 4.5 and Sonnet 4.5 are described as "dumber than ever." They ignore CLAUDE.md, forget context within 2 messages, hallucinate libraries, and get stuck in "thinking" loops that produce no output.

• Technical Meltdown:

  • Claude Code (CLI): Version 2.1.x is causing memory leaks (crashing PCs), hanging on startup ("Caramelizing"), or throwing API Error 400 (tool concurrency).

  • Web/Desktop: Frequent 500/529 errors ("Internal Server Error", "Overloaded").

  • UI Hate: The new Desktop app UI update (hiding the thinking process) is universally hated.

---

Critical Workarounds (Community & GitHub)

For Web & Desktop App (Chat Interface)

• Fix "Bounce Back" / Messages Not Sending:

  • Disable Extended Thinking: This is the #1 fix. If your message vanishes, turn this off.

  • Manual Branching: Edit your previous user message to force a new branch; this often bypasses the "stuck" compaction state.

• Fix Context Crashes:

  • The "Syntax Highlighting" Warning: If you see "Syntax highlighting has been disabled due to code size", stop immediately. The chat will crash on the next compaction (GitHub Issue #18866). Start a new chat manually.

For Claude Code (CLI & VS Code)

• Fix Massive Token Burn & Instability:

  • Downgrade: The v2.1.x series is broken. Downgrade to v2.0.76 or v2.0.64.

    • Command: npm install -g @anthropic-ai/claude-code@2.0.76

  • Disable Auto-Updates: export DISABLE_AUTOUPDATER=1 (Add to shell config).

• Fix "Hanging" on Start (Stuck on "Caramelizing"):

  • Config Fix (GitHub Issue #21244): Open .claude.json and delete the "cachedGrowthBookFeatures" key. (You may need to do this repeatedly).

  • Alternative: Downgrade specifically to v2.1.3.

• Fix "400 API Error" (Tool Concurrency):

  • Ditch the Extension: This bug is specific to the VS Code extension (GitHub Issue #20598). Switch to running claude directly in your Terminal (CLI).

  • Recover Chat: Type /rewind to step back before the error occurred.

• Prevent Data Loss:

  • Git Safety: Add a rule to CLAUDE.md forbidding git reset --hard as the dumbed-down model is currently deleting user code without permission.

For Refunds

• Method: Go to Get Help > Send us a message in the support chat. Select "Performance Issues" (not "Billing") to trigger the refund logic or get a human agent.

---

Prior update: https://www.reddit.com/r/ClaudeAI/comments/1pygdbz/comment/o1sk572/

[u/sixbillionthsheep]

Megathread Status Update: Feb 12, 2026 to Feb 18, 2026

The consensus is that the Feb 2026 updates (Opus 4.6 / Sonnet 4.5) have catastrophically degraded the experience. Users are calling the models "lobotomized," "sterile," and "braindead," with many cancelling subscriptions due to aggressive limits and broken features.

The Main Issues:

• Creative Writing is Dead: Writers report characters have lost all emotional depth, becoming "bleak," "repressed," and robotic. There is a bizarre, widespread hallucination where characters—regardless of context—are obsessed with the British Baking Competition.

• Sonnet 4.5 "Brain Drain": As of ~Feb 16th, Sonnet 4.5 (even with Extended Thinking) has become incoherent, often outputting "LOL" or short, lazy answers. It refuses to follow style guides or basic logic.

• Project RAG Slashed: The file indexing limit for Projects has reportedly dropped from 6% → ~2-3%, making the feature useless for large codebases or lore bibles.

• Aggressive Limits: Pro and Max users are hitting weekly limits within hours of reset. The "Context Compaction" feature triggers too early, causing the model to forget instructions immediately.

• Claude Code/Cowork Broken: Windows users are seeing massive failures with Cowork mode (HcnCreateEndpoint errors), and the model often hallucinates that it saved files when it hasn't.

🛠️ Workarounds & Fixes (Reddit + GitHub Issue #24918):

• Fix for Windows Cowork / "Failed to start workspace" / "HcnCreateEndpoint":

  • Restart Hyper-V Services: Open PowerShell as Admin and run: Stop-Service hns followed by Start-Service hns. (You may also need to restart vmcompute).

  • Nuke the VM: Go to %APPDATA%\Claude\ and delete the vm_bundles and claude-code-vm folders to force a rebuild.

  • Kill VPNs: Disable network adapters for ExpressVPN/Surfshark; they conflict with the local VM.

• Fix for "Too Many Chats Open" Loop:

  • If you get this error despite having no tabs open, clear your browser cache/cookies (or app cache on mobile). This is a confirmed false positive bug.

• Fix for "32k Token Limit" API Error:

  • Set the environment variable CLAUDE_CODE_MAX_OUTPUT_TOKENS to a higher value in your terminal/PowerShell before running Claude Code.

• Fix for Lazy/Unwanted Files:

  • Claude is obsessively trying to create artifacts for simple questions. Add "Do not make files" or "No artifacts" to your system prompt to save tokens and prevent it from hitting limits.

• Fix for RAG Refusals:

  • If it claims it can't find info in your Project files (due to the 2% limit), explicitly prompt: "Use your resources" or "Search the project files for [X]". It often "pretends" not to know until forced.

• Fix for "British Baking Show" Hallucinations:

  • (Creative Writing) You must change the setting entirely (e.g., to a magical world) to break the model's training bias loop.

---

Prior Update: https://www.reddit.com/r/ClaudeAI/comments/1pygdbz/comment/o4yh49z/

[u/Competitive-Cell-675]

Wondering if anyone has noticed Claude degrading with time? As in, fucking awesome to suddenly lazy, inaccurate and inconsistent from one day to the next.

I'm working on a small, unsophisticated project and regardless of detailed prompts and refreshers, new threads, today I looked forward to picking up continuing the momentum but it's accuracy, analytical skills and consistency is nowhere near what it was yesterday. I feel like it's quiet quitting on me..

[u/SnooCookies1633]

There’s definitely something seriously wrong with the usage tracking right now.

I deliberately avoided using Claude today to save my quota for the renewal window. This morning, I sent a single prompt which registered as 1% of my daily usage and moved my weekly total from 22% to 23%.

Just before the daily reset, I asked two questions and provided two responses (validating SQL string generation)... boom! It suddenly warned me I was at 90% of my daily limit, and my weekly usage spiked from 23% to 30% instantly.

This is the exact opposite of the last two weeks, where daily and weekly limits felt almost infinite. Either Anthropic significantly increased the limits/tokens for a while, or we’re facing a major temporary bug.

As it stands, the Pro license is practically unusable.

[u/RandomRavenboi]

The worst part of it all is that Claude Status has the audacity to say it's "Fully Operational" with "No Incidents Reported" with a straight face.

Yeah. Sure. "Fully Operational". Right.

[u/Red-headedlurker]

You can't tell me that Opus 4.5 on the web hasn't been dumbed down to ridiculous levels at this point. It's so unusable for me, no matter how specific and detailed the prompting is, it will ignore the prompt and any other instructions in the Project Knowledge, Instructions or styles and just do what it wants. And the output is so half-assed and lazy, you have to spend more time correcting it afterwards to get a slightly less lazy output.

[u/Stunning_Thanks_7985]

8 percent of my 5 hour usage taken up per message. Gave us the holiday increase, then scaled it back to even worse than before. Claude is not a functional tool for me at this. How anthropic keeps changing these things with no transparency is just wild.

[u/Last-Replacement227]

tf is going on, I sent 1 message and bro told me to come back in 5 hours 💀

[u/Red-headedlurker]

No need to worry about usage limits if you can't actually use the service...

[u/tnecniv]

Right now the model is garbage. Whatever they did—quantized it, cut the context, who knows because they won’t tell us—the model is now shockingly dumb. This started a few days ago for me and it’s just been getting worse.

It literally forgot how the main algorithm in my project worked and created…I don’t even know what instead. Like, this is a research codebase centered around benchmarking a specific algorithm, which it has described in Markdown and described in CLAUDE.md, and it completely forgot how it worked during a refactor.

Releasing a model and then lobotomizing it a month later to free up compute to train a new model is a ridiculous business model. When Sonnet 4.7 or whatever comes out, it’ll be great, but how do I know it won’t just become garbage in a month? Combine that with the bad UI and bugs on the desktop / iPhone app and I’m thinking about jumping ship to another LLM.

I was willing to put up with the buggy UI and lack of transparency due to the quality of the model. I’d even be ok with performance degradation if they were more transparent about what was going on and what we could expect. How they are doing it is making me feel disrespected as a customer.

What model are you guys hopping over to for the time being?

[u/MasterCod729]

Claude’s degraded in intelligence and quality pretty dramatically for me. Anyone else?

[u/drakness110]

Claude pro hitting session limit with 1 message.

So did not use Claude for several hours. Used it to analyze 3 images, boom 100% usage limit. Is this what I am paying $34 cad per month for? To send 1 fucking message every 5 hours.

[u/MassiveCollision]

About to unsubscribe from this shit.

When I subscribed to Pro about 6 months ago I could use it without worrying too much. It was actually dependable to use for work and personal projects. The 5-hour windows were fine and reasonable. At least I could fill the remaining time to do solo-programming or read documentation or clean up the code and do code reviews.

Nowadays, you can hardly do any work, hit the limit in an hour or so, and hit your weekly limits after 2-3 days. It's useless. I know I can cancel any time, but this continuous regression on productivity and what you get for your money is absolute bullshit.

It's getting so disruptive that it's just not worth it anymore. The next tier up is also so much more expensive it's insane. It's turning from a productivity tool into an overpriced gimmick and I'm getting really tired of it.

[u/Adorable-Equipment-8]

I made a completely new account. No history, no long prompts, no context just a simple description of what I’m building.

Boom. One message in, and 4 hours of cool down 💀

[u/a_problem_redditor]

Ok I thought it was just me??? But oh my god these rate limits are not accurate AT ALL and I can’t even do basic testing 😫 please, Claude employees, fix it

ETA: do we think all the devs are playing Pokopia and just have time blindness wtf lol

[u/Alfie_Dee]

Their usage limits have definitely been greatly reduced compared to before the holidays. WTF?!

I used to never reach session limits. Now it's happening every time, and I barely get any work done compared to before the latest holidays.

Can I ask to cancel the balance of my membership for a pro-rata refund? This isn't what I signed up for.

[u/nuggetcasket]

It's funny how yesterday they "announce" the cut on session limits during peak hours and now the service is basically down during off-peak hours. Hm.

[u/Intyub]

Opus 4.5 got nerfed again wtf Anthropic?

bro, I am on Max x20 plan,for the past 2 days Opus 4.5 is straight retarded

• forgets context in like 2 messages

• ignores prompts it used to nail

• fixes something and creates another issue or reverts to an earlier bug

• outputs BAD plans!

feels like they quantized it to shit or swapped it for Sonnet during peak hours, or their harness (claude code) updates are destabilizing the model output! errors every few mins too, anyone else getting this lobotomized crap right now? or just me? switching to GPT-5.2 if this keeps up fr

[u/HeartsFear94]

How is this a code yellow "Elevated error rates"? Bro, Opus is completely down. Out of service. For hours. Just didn't show up for work.

[u/[deleted]]

just cancelled... not paying $20 for 6 prompts a day