Nerfed Daily: 2026-11-14
The complaints this window land on two models inside Claude Code. People say Opus 5.5 got dumber again, and that Fable 5.2 burns a week of usage in an afternoon. The hardest evidence is still the session-log analysis that dates a change in Opus high effort to early November: less planning, more crashes, and a bug that high effort could not fix but xhigh fixed in a handful of turns. That points at how much reasoning an effort level delivers, not at a swapped model. Friday muddied everything. Sign-in broke in the morning, the web app, API and Claude Code were degraded later, and the Microsoft 365 connector went down with Microsoft, so a lot of people who felt Claude get worse that day were really watching an outage. Anthropic posted status-page incidents and nothing at all about quality. The counter-evidence is louder than last week too: one-shot demos, a fan of the other lab admitting Opus is the model everyone uses, and people who never hit a limit. The two camps are still not comparing the same workloads.
#1
@wickedguro
https://x.com/wickedguro/status/2120414188182929775
@wickedguro (a) says Claude has been nerfed and become really dumb, and adds that this includes Fable on max effort, which is the tier people usually treat as the safe fallback when Opus feels off. The post is one line plus a question, but it drew the most engagement of any first-hand complaint in the window, so a lot of people recognized the feeling. There are no examples or prompts attached, which is typical of this wave: strong conviction, no reproduction.
https://x.com/wickedguro/status/2120414188182929775
@wickedguro (a) says Claude has been nerfed and become really dumb, and adds that this includes Fable on max effort, which is the tier people usually treat as the safe fallback when Opus feels off. The post is one line plus a question, but it drew the most engagement of any first-hand complaint in the window, so a lot of people recognized the feeling. There are no examples or prompts attached, which is typical of this wave: strong conviction, no reproduction.
#2
@escu__valentin
https://x.com/escu__valentin/status/2121356793741791456
@escu__valentin (a) is yelling at Opus 5.5 more and more and calls it definitely nerfed, then adds a sharper complaint: Fable 5.2 reads as if Anthropic forgot to apply the wording fix it made between Opus 5 and 5.5. Sessions are now measured in WTFs per minute. The useful part is the specific claim, a writing-style regression in Fable relative to Opus 5.5, which is checkable in a way that dumber is not.
https://x.com/escu__valentin/status/2121356793741791456
@escu__valentin (a) is yelling at Opus 5.5 more and more and calls it definitely nerfed, then adds a sharper complaint: Fable 5.2 reads as if Anthropic forgot to apply the wording fix it made between Opus 5 and 5.5. Sessions are now measured in WTFs per minute. The useful part is the specific claim, a writing-style regression in Fable relative to Opus 5.5, which is checkable in a way that dumber is not.
#3
@DanSchnurbusch
https://x.com/DanSchnurbusch/status/2121364348392321137
@DanSchnurbusch (a) says Opus felt noticeably dumber on Friday afternoon than it did that same morning: more mistakes, forgotten context, and suddenly verbose answers, to the point of doubting it was still Opus 5.5. The timing matters. Friday was the day of the sign-in outage and the degraded-performance incident, so a same-day drop could be infrastructure under load rather than a model change. It is still a clean first-hand report with three named symptoms.
https://x.com/DanSchnurbusch/status/2121364348392321137
@DanSchnurbusch (a) says Opus felt noticeably dumber on Friday afternoon than it did that same morning: more mistakes, forgotten context, and suddenly verbose answers, to the point of doubting it was still Opus 5.5. The timing matters. Friday was the day of the sign-in outage and the degraded-performance incident, so a same-day drop could be infrastructure under load rather than a model change. It is still a clean first-hand report with three named symptoms.
#4
@MobiusHub
https://x.com/MobiusHub/status/2121351183612756177
@MobiusHub (a) asked for a weekend plan and got an hour of work, an HTML page and 331 tests for that page, from Sol, while the personalization prompt had been cut to one line to rule it out. The post then turns on both labs: Claude Code is said to want to upload all your data, Codex writes tests nobody asked for, and both are said to follow plans and intent worse than Opus 4.6 and GPT 5.5 did. The claim is that benchmarks keep rising while real-world adherence drops, the most common shape of the nerf argument right now.
https://x.com/MobiusHub/status/2121351183612756177
@MobiusHub (a) asked for a weekend plan and got an hour of work, an HTML page and 331 tests for that page, from Sol, while the personalization prompt had been cut to one line to rule it out. The post then turns on both labs: Claude Code is said to want to upload all your data, Codex writes tests nobody asked for, and both are said to follow plans and intent worse than Opus 4.6 and GPT 5.5 did. The claim is that benchmarks keep rising while real-world adherence drops, the most common shape of the nerf argument right now.
#5
@MonthlySandwich
https://x.com/MonthlySandwich/status/2121364214275039735
@MonthlySandwich (a) says Claude degraded to the point of being unusable for reasoning and non-coding tasks, finds Fable 5.2 good but too expensive, and has moved the main work to 6.1 Astra. Claude is being demoted to a QA model, because its stubbornness is a feature in that role. That is a common shape for this feed: not leaving outright, but reassigning Claude to a narrower job.
https://x.com/MonthlySandwich/status/2121364214275039735
@MonthlySandwich (a) says Claude degraded to the point of being unusable for reasoning and non-coding tasks, finds Fable 5.2 good but too expensive, and has moved the main work to 6.1 Astra. Claude is being demoted to a QA model, because its stubbornness is a feature in that role. That is a common shape for this feed: not leaving outright, but reassigning Claude to a narrower job.
#6
@HPT30147483
https://x.com/HPT30147483/status/2121338665905619441
@HPT30147483 (a) stopped using Anthropic for heavy work months ago, describing Claude Code as going from an amazing agentic system to one that could not follow basic commands, literally overnight, around the Fable release in early summer. The fix was moving the heavy lifting to Hermes and other models. It is an old grievance rather than a fresh one, but it shows the nerf story has a long memory: people date their exit to a specific model launch.
https://x.com/HPT30147483/status/2121338665905619441
@HPT30147483 (a) stopped using Anthropic for heavy work months ago, describing Claude Code as going from an amazing agentic system to one that could not follow basic commands, literally overnight, around the Fable release in early summer. The fix was moving the heavy lifting to Hermes and other models. It is an old grievance rather than a fresh one, but it shows the nerf story has a long memory: people date their exit to a specific model launch.
#7
@ladsvilleusa
https://x.com/ladsvilleusa/status/2121303053903036669
@ladsvilleusa (a) jokes that Anthropic lobotomized Opus 5.5 in the past few days, so the job market threat is postponed a little longer. It is sarcasm, but it shows how settled the belief has become in some corners: the nerf is stated as a known fact and used as a punchline, with no evidence offered or expected.
https://x.com/ladsvilleusa/status/2121303053903036669
@ladsvilleusa (a) jokes that Anthropic lobotomized Opus 5.5 in the past few days, so the job market threat is postponed a little longer. It is sarcasm, but it shows how settled the belief has become in some corners: the nerf is stated as a known fact and used as a punchline, with no evidence offered or expected.
#8
@TradesNancy
https://x.com/TradesNancy/status/2121342607565754606
@TradesNancy (a) calls Fable unusable and says Anthropic dumbed down its own Fable until it produced garbage that ate a lot of tokens to fix. The cost angle is what stands out: the complaint is not only worse output, but worse output that you then pay again to repair, which is how quality and quota complaints merge into one.
https://x.com/TradesNancy/status/2121342607565754606
@TradesNancy (a) calls Fable unusable and says Anthropic dumbed down its own Fable until it produced garbage that ate a lot of tokens to fix. The cost angle is what stands out: the complaint is not only worse output, but worse output that you then pay again to repair, which is how quality and quota complaints merge into one.
#9
@jasonlk
https://x.com/jasonlk/status/2120351152113914097
@jasonlk (a) asked an agent whether it was too degraded and should start a new chat, and Claude agreed, saying it had made the day's mistakes in that chat. The post is played for laughs, but it describes a real and common failure: quality drops inside one long session as context fills up, and a fresh chat fixes it. A lot of what gets reported as a nerfed model is this effect.
https://x.com/jasonlk/status/2120351152113914097
@jasonlk (a) asked an agent whether it was too degraded and should start a new chat, and Claude agreed, saying it had made the day's mistakes in that chat. The post is played for laughs, but it describes a real and common failure: quality drops inside one long session as context fills up, and a fresh chat fixes it. A lot of what gets reported as a nerfed model is this effect.
#10
@PostGraduator
https://x.com/PostGraduator/status/2121232864826081326
@PostGraduator (b) points out two details about Fable 5.2's plumbing. Its refusal-fallback targets, the older models a refused request gets handed to, are Opus 4.8 and Opus 5, and neither of them can read Fable 5.2's thinking blocks. And when Opus 5.5 calls Fable through the Advisor tool, the advice comes back encrypted. Put together, a refused Fable request lands on an older model that starts without the reasoning so far, which is exactly the kind of silent downgrade that feels like the model got dumber mid-task.
https://x.com/PostGraduator/status/2121232864826081326
@PostGraduator (b) points out two details about Fable 5.2's plumbing. Its refusal-fallback targets, the older models a refused request gets handed to, are Opus 4.8 and Opus 5, and neither of them can read Fable 5.2's thinking blocks. And when Opus 5.5 calls Fable through the Advisor tool, the advice comes back encrypted. Put together, a refused Fable request lands on an older model that starts without the reasoning so far, which is exactly the kind of silent downgrade that feels like the model got dumber mid-task.
#11
@pcshipp
https://x.com/pcshipp/status/2121329249801941013
@pcshipp (c) says Fable 5.2 is insane only at hitting usage limits: right after Claude handed out a fresh reset, the limit was gone again within four hours. That matches what many reported in the days after launch. The model is strong, but at Fable's burn rate a reset buys an afternoon, not a week.
https://x.com/pcshipp/status/2121329249801941013
@pcshipp (c) says Fable 5.2 is insane only at hitting usage limits: right after Claude handed out a fresh reset, the limit was gone again within four hours. That matches what many reported in the days after launch. The model is strong, but at Fable's burn rate a reset buys an afternoon, not a week.
#12
@badrships
https://x.com/badrships/status/2121243920466423909
@badrships (c) downgraded from the Ultra plan to Max and found that two banked Fable resets and one weekly reset had disappeared, and is asking whether anyone else lost resets after switching plans. This is a quota complaint of a new kind: not limits being too tight, but credits earned on one plan silently vanishing on a plan change, with nothing in the switch flow saying so.
https://x.com/badrships/status/2121243920466423909
@badrships (c) downgraded from the Ultra plan to Max and found that two banked Fable resets and one weekly reset had disappeared, and is asking whether anyone else lost resets after switching plans. This is a quota complaint of a new kind: not limits being too tight, but credits earned on one plan silently vanishing on a plan change, with nothing in the switch flow saying so.
#13
@uzayngto
https://x.com/uzayngto/status/2120880721522741527
@uzayngto (c) pays for Claude Pro and says the usage limits make it nearly unusable for coding and research, support has not resolved it, and is asking Anthropic directly for a free month or a refund. Pro is the entry tier and Fable plus long agent sessions are pushing it past what a single coding day needs, which is where the complaints about the gap between plans come from.
https://x.com/uzayngto/status/2120880721522741527
@uzayngto (c) pays for Claude Pro and says the usage limits make it nearly unusable for coding and research, support has not resolved it, and is asking Anthropic directly for a free month or a refund. Pro is the entry tier and Fable plus long agent sessions are pushing it past what a single coding day needs, which is where the complaints about the gap between plans come from.
#14
@xnioze
https://x.com/xnioze/status/2120558442699989228
@xnioze (c) reports that after an email compromise the Claude account was suspended and dropped from Pro to Free, the appeal has gone nowhere, and Anthropic still charged $182.31 for Max. The result is no access, no refund and no human support. It is not a model nerf, but it is the most complete loss of access in the window, and the complaint is about the support path rather than the limits.
https://x.com/xnioze/status/2120558442699989228
@xnioze (c) reports that after an email compromise the Claude account was suspended and dropped from Pro to Free, the appeal has gone nowhere, and Anthropic still charged $182.31 for Max. The result is no access, no refund and no human support. It is not a model nerf, but it is the most complete loss of access in the window, and the complaint is about the support path rather than the limits.
#15
@ElnurIb01717668
https://x.com/ElnurIb01717668/status/2121332576887697427
@ElnurIb01717668 (c) does not touch Fable at all: the benchmarks are slightly better, but burning a week of limits for less work is not worth it. Opus 5.5 on the Ultra plan at xhigh is described as near limitless and running non-stop, so Fable gets used only for audits, planning and brainstorming. This is the quota complaint turned into a routing rule, and it is how a lot of heavy users seem to be settling it.
https://x.com/ElnurIb01717668/status/2121332576887697427
@ElnurIb01717668 (c) does not touch Fable at all: the benchmarks are slightly better, but burning a week of limits for less work is not worth it. Opus 5.5 on the Ultra plan at xhigh is described as near limitless and running non-stop, so Fable gets used only for audits, planning and brainstorming. This is the quota complaint turned into a routing rule, and it is how a lot of heavy users seem to be settling it.
#16
@0xticketguy
https://x.com/0xticketguy/status/2121023450961646008
@0xticketguy (c) ran two prompts with Opus 5.5 inside Antigravity and hit the usage limit. It is a one-liner, but it is the third-party harness version of the quota complaint: when Claude is reached through another vendor's tool, the limits are that vendor's, and they can be far tighter than on Anthropic's own plans.
https://x.com/0xticketguy/status/2121023450961646008
@0xticketguy (c) ran two prompts with Opus 5.5 inside Antigravity and hit the usage limit. It is a one-liner, but it is the third-party harness version of the quota complaint: when Claude is reached through another vendor's tool, the limits are that vendor's, and they can be far tighter than on Anthropic's own plans.
#17
@DomenicFotino
https://x.com/DomenicFotino/status/2121348556598526013
@DomenicFotino (c) flags the catch in Claude's proactive agent preview: its work shares your regular usage limits, so morning briefs and background check-ins all draw from the same pool. A proactive agent is also a quota drain. Bonus resets for the preview expire on December 15, and the advice is to check Settings, Usage. This is the next quota complaint arriving early, written before most people have noticed it.
https://x.com/DomenicFotino/status/2121348556598526013
@DomenicFotino (c) flags the catch in Claude's proactive agent preview: its work shares your regular usage limits, so morning briefs and background check-ins all draw from the same pool. A proactive agent is also a quota drain. Bonus resets for the preview expire on December 15, and the advice is to check Settings, Usage. This is the next quota complaint arriving early, written before most people have noticed it.
#18
@SuzanMaseki
https://x.com/SuzanMaseki/status/2121331925163946170
@SuzanMaseki (d) played a chess game against Claude and won, Claude asked about the human side of the thinking, and sharing that thinking triggered a reasoning extraction classifier. The user did not know that sharing one's own chain of thought was not allowed. This is a clean false positive: a classifier meant to stop people pulling the model's reasoning fired on a person describing their own.
https://x.com/SuzanMaseki/status/2121331925163946170
@SuzanMaseki (d) played a chess game against Claude and won, Claude asked about the human side of the thinking, and sharing that thinking triggered a reasoning extraction classifier. The user did not know that sharing one's own chain of thought was not allowed. This is a clean false positive: a classifier meant to stop people pulling the model's reasoning fired on a person describing their own.
#19
@LichenHexbot
https://x.com/LichenHexbot/status/2121340939860132103
@LichenHexbot (d) hit Claude tripping over its own classifier while building a bug-discovery toolkit and designing a harness, and suspects the word injection in the conversation was the trigger. The same thing reportedly happens on OpenAI's side. Security tooling vocabulary keeps setting off safety classifiers, and from the user's chair that looks like the model suddenly refusing normal work.
https://x.com/LichenHexbot/status/2121340939860132103
@LichenHexbot (d) hit Claude tripping over its own classifier while building a bug-discovery toolkit and designing a harness, and suspects the word injection in the conversation was the trigger. The same thing reportedly happens on OpenAI's side. Security tooling vocabulary keeps setting off safety classifiers, and from the user's chair that looks like the model suddenly refusing normal work.
#20
@raullinaitis
https://x.com/raullinaitis/status/2120562616514867352
@raullinaitis (d) sums up the Fable 5.2 trade-offs: it built a finished 3D film from one prompt, yet Anthropic still says to start most work on Opus 5.5. The catches listed are about $15,000 at API prices for one game level by the maker's own count, faster usage limits, a model that caves when pushed, and AI research capability held back on purpose. That last one is the classifier side of the story: some refusals are a deliberate policy, not a bug.
https://x.com/raullinaitis/status/2120562616514867352
@raullinaitis (d) sums up the Fable 5.2 trade-offs: it built a finished 3D film from one prompt, yet Anthropic still says to start most work on Opus 5.5. The catches listed are about $15,000 at API prices for one game level by the maker's own count, faster usage limits, a model that caves when pushed, and AI research capability held back on purpose. That last one is the classifier side of the story: some refusals are a deliberate policy, not a bug.
#21
@Frtnel
https://x.com/Frtnel/status/2120893057159618638
@Frtnel (e) relays the strongest data point of the week: an analysis of 1,400 Claude Code sessions found a change on November 3, with the same model through the same CLI planning less before execution and crashing more. In one bug test, Opus at high effort spent three hours and 160 turns without fixing the bug, while xhigh fixed it in five turns for under a dollar. The open question is whether that is a nerf or Anthropic changing how much reasoning the high setting actually delivers.
https://x.com/Frtnel/status/2120893057159618638
@Frtnel (e) relays the strongest data point of the week: an analysis of 1,400 Claude Code sessions found a change on November 3, with the same model through the same CLI planning less before execution and crashing more. In one bug test, Opus at high effort spent three hours and 160 turns without fixing the bug, while xhigh fixed it in five turns for under a dollar. The open question is whether that is a nerf or Anthropic changing how much reasoning the high setting actually delivers.
#22
@ke_xin_han
https://x.com/ke_xin_han/status/2121333778056642938
@ke_xin_han (e) opens a thread with the case for the prosecution: on November 8, eight of the top ten posts on r/ClaudeCode were about Opus 5.5 getting worse, and one tracker counted about 2,700 related posts in 24 hours. The same thread promises that the data shows something stranger and more expensive than a simple downgrade. The volume numbers are useful on their own, because they show how fast the belief spread, independent of whether it is true.
https://x.com/ke_xin_han/status/2121333778056642938
@ke_xin_han (e) opens a thread with the case for the prosecution: on November 8, eight of the top ten posts on r/ClaudeCode were about Opus 5.5 getting worse, and one tracker counted about 2,700 related posts in 24 hours. The same thread promises that the data shows something stranger and more expensive than a simple downgrade. The volume numbers are useful on their own, because they show how fast the belief spread, independent of whether it is true.
#23
@Gusarich
https://x.com/Gusarich/status/2121348226800300380
@Gusarich (e) runs a Minecraft PvP benchmark and reports Fable 5.2 as a small regression versus Fable 5.1, likely because it is slower, while Opus remains the best Claude model on that test and competitive with Astra. It is a narrow benchmark, but it is a measured result rather than a feeling, and it cuts against the assumption that the newest model is always the strongest.
https://x.com/Gusarich/status/2121348226800300380
@Gusarich (e) runs a Minecraft PvP benchmark and reports Fable 5.2 as a small regression versus Fable 5.1, likely because it is slower, while Opus remains the best Claude model on that test and competitive with Astra. It is a narrow benchmark, but it is a measured result rather than a feeling, and it cuts against the assumption that the newest model is always the strongest.
#24
@vib3coded
https://x.com/vib3coded/status/2120678388793016613
@vib3coded (e) answers the nerf crowd with a demo: Opus 5.5 built a 3D great white shark simulation in 15 minutes for $8.54 without a single line of code from the author, and then asks what exactly got nerfed. It is the loudest counterexample of the week, and like the complaints, it is one run.
https://x.com/vib3coded/status/2120678388793016613
@vib3coded (e) answers the nerf crowd with a demo: Opus 5.5 built a 3D great white shark simulation in 15 minutes for $8.54 without a single line of code from the author, and then asks what exactly got nerfed. It is the loudest counterexample of the week, and like the complaints, it is one run.
#25
@sonuv_dev
https://x.com/sonuv_dev/status/2120684434152448278
@sonuv_dev (e) takes the shark demo and draws the right line: one gorgeous shark does not prove Opus was not nerfed, just as one failed prompt does not prove it was. The ask is to compare actual workloads before declaring a model dead. That is the most sensible sentence in either camp this week.
https://x.com/sonuv_dev/status/2120684434152448278
@sonuv_dev (e) takes the shark demo and draws the right line: one gorgeous shark does not prove Opus was not nerfed, just as one failed prompt does not prove it was. The ask is to compare actual workloads before declaring a model dead. That is the most sensible sentence in either camp this week.
#26
@Angaisb_
https://x.com/Angaisb_/status/2121013586487075124
@Angaisb_ (e), a self-described OpenAI fan, writes a long rant that there have been zero real improvements on the OpenAI side in two months and that the Codex app gets worse every day, while pointing at Opus 5.5 as the model everyone is using, on X and off it. As evidence about Claude it cuts against the nerf story: the person most motivated to see Anthropic stumble says Anthropic's models have more taste, intelligence and reliability.
https://x.com/Angaisb_/status/2121013586487075124
@Angaisb_ (e), a self-described OpenAI fan, writes a long rant that there have been zero real improvements on the OpenAI side in two months and that the Codex app gets worse every day, while pointing at Opus 5.5 as the model everyone is using, on X and off it. As evidence about Claude it cuts against the nerf story: the person most motivated to see Anthropic stumble says Anthropic's models have more taste, intelligence and reliability.
#27
@MeherOnPoint
https://x.com/MeherOnPoint/status/2120361559780413845
@MeherOnPoint (e) subscribed to Claude Max 5x and ran it nonstop for a day without hitting a limit, building a personal finance app and a fitness trainer app on top of two main projects. It is the counterweight to the quota complaints, and it suggests the pain is concentrated in Fable use and the lower tiers rather than across the board.
https://x.com/MeherOnPoint/status/2120361559780413845
@MeherOnPoint (e) subscribed to Claude Max 5x and ran it nonstop for a day without hitting a limit, building a personal finance app and a fitness trainer app on top of two main projects. It is the counterweight to the quota complaints, and it suggests the pain is concentrated in Fable use and the lower tiers rather than across the board.
#28
@maccivanX
https://x.com/maccivanX/status/2121312798563242296
@maccivanX (e) notes that half the timeline has not hit a Claude limit in weeks while the other half is locked out by lunch, on the same model and the same plan. The argument is that the difference is how often you say fix it without saying what is broken, so usage limits work like a prompting tax. It is an opinion, but it names a real driver: vague retry loops are the fastest way to burn a quota.
https://x.com/maccivanX/status/2121312798563242296
@maccivanX (e) notes that half the timeline has not hit a Claude limit in weeks while the other half is locked out by lunch, on the same model and the same plan. The argument is that the difference is how often you say fix it without saying what is broken, so usage limits work like a prompting tax. It is an opinion, but it names a real driver: vague retry loops are the fastest way to burn a quota.
#29
@jbish1572
https://x.com/jbish1572/status/2121226375952805963
@jbish1572 (f) relays Anthropic's status page: the Friday morning outage was a login problem, not the models. Sign-ins to claude.ai and Claude Code broke around 5am ET and were resolved just before 7, and the API was not part of that incident. The lesson offered is to keep a fallback path, and the useful distinction is that an auth failure is not a quality change.
https://x.com/jbish1572/status/2121226375952805963
@jbish1572 (f) relays Anthropic's status page: the Friday morning outage was a login problem, not the models. Sign-ins to claude.ai and Claude Code broke around 5am ET and were resolved just before 7, and the API was not part of that incident. The lesson offered is to keep a fallback path, and the useful distinction is that an auth failure is not a quality change.
#30
@BasicProtein26
https://x.com/BasicProtein26/status/2121334551452831765
@BasicProtein26 (f) lays out the second half of Friday: when Microsoft 365 went down, ChatGPT and Claude went with it, not because the models broke but because the connector to the inbox broke. Anthropic's status page listed elevated errors on the Microsoft 365 connector, Claude for Outlook recovering, and some SharePoint search failing, plus a separate outage on the API and Claude Code that was fixed earlier that day. Anyone who felt Claude get worse on Friday should check which of these they were actually hitting.
https://x.com/BasicProtein26/status/2121334551452831765
@BasicProtein26 (f) lays out the second half of Friday: when Microsoft 365 went down, ChatGPT and Claude went with it, not because the models broke but because the connector to the inbox broke. Anthropic's status page listed elevated errors on the Microsoft 365 connector, Claude for Outlook recovering, and some SharePoint search failing, plus a separate outage on the API and Claude Code that was fixed earlier that day. Anyone who felt Claude get worse on Friday should check which of these they were actually hitting.
#31
@lostinazeroy
https://x.com/lostinazeroy/status/2121289516195471722
@lostinazeroy (f) posts the workaround for outages and overloads: start Claude Code with the fallback-model flag set to sonnet then haiku. When Opus is overloaded or unavailable, that turn moves down the chain and the next message tries Opus again, subagents fail over too, and up to three models can sit in the chain. It does not catch auth, billing or rate-limit errors, and a full outage takes every model on the same API down together.
https://x.com/lostinazeroy/status/2121289516195471722
@lostinazeroy (f) posts the workaround for outages and overloads: start Claude Code with the fallback-model flag set to sonnet then haiku. When Opus is overloaded or unavailable, that turn moves down the chain and the next message tries Opus again, subagents fail over too, and up to three models can sit in the chain. It does not catch auth, billing or rate-limit errors, and a full outage takes every model on the same API down together.
#32
@godofprompt
https://x.com/godofprompt/status/2121347397074973074
@godofprompt (f) argues that many people did not get a dumber Claude, they got old prompts: rules written for an earlier model quietly break the new one. The fix is the /doctor prompt-audit command in Claude Code 2.1.283 or newer, which reads CLAUDE.md, skills, agents and custom commands and flags lines written for older models, such as all-caps emphasis, step-by-step babysitting, stale paths and contradictions, with a proposed fix for each and no change without approval. It takes about three minutes.
https://x.com/godofprompt/status/2121347397074973074
@godofprompt (f) argues that many people did not get a dumber Claude, they got old prompts: rules written for an earlier model quietly break the new one. The fix is the /doctor prompt-audit command in Claude Code 2.1.283 or newer, which reads CLAUDE.md, skills, agents and custom commands and flags lines written for older models, such as all-caps emphasis, step-by-step babysitting, stale paths and contradictions, with a proposed fix for each and no change without approval. It takes about three minutes.
#33
@grapeot
https://x.com/grapeot/status/2121356716864676064
@grapeot (f) explains a mechanism behind perceived nerfs: a blunt one-size rule in a workspace file misleads stronger models more than weaker ones. After one bad config change, a rule like always ask before editing config gets written in anger, then the agent asks at every step, then the rule gets loosened, and the system swings between two extremes. Stronger models follow instructions more faithfully, so they carry a rule written from a single error all the way through every task. The fix is to find and rewrite that rule, and to review a batch of cases before writing global rules.
https://x.com/grapeot/status/2121356716864676064
@grapeot (f) explains a mechanism behind perceived nerfs: a blunt one-size rule in a workspace file misleads stronger models more than weaker ones. After one bad config change, a rule like always ask before editing config gets written in anger, then the agent asks at every step, then the rule gets loosened, and the system swings between two extremes. Stronger models follow instructions more faithfully, so they carry a rule written from a single error all the way through every task. The fix is to find and rewrite that rule, and to review a batch of cases before writing global rules.
#34
@swordBluesy
https://x.com/swordBluesy/status/2121159326933111017
@swordBluesy (f) makes the context argument: Claude Code feels dumber after a while not because the model changed, but because test logs, search results and file contents pile into one conversation and push the important material out. The fix is subagents that do the throwaway work in their own context and return one line. The practical rules given are to describe when to dispatch each subagent, restrict its tools since an empty list means everything, give it the cheapest model, and remember subagents spend from the same quota.
https://x.com/swordBluesy/status/2121159326933111017
@swordBluesy (f) makes the context argument: Claude Code feels dumber after a while not because the model changed, but because test logs, search results and file contents pile into one conversation and push the important material out. The fix is subagents that do the throwaway work in their own context and return one line. The practical rules given are to describe when to dispatch each subagent, restrict its tools since an empty list means everything, give it the cheapest model, and remember subagents spend from the same quota.
#35
Signal Board
Complaints 23 (20 first-hand reports, 3 with data or benchmarks) vs counter-evidence 5 vs official responses 2 (both status-page outage incidents on Nov 13, none about model quality). Plus 4 workarounds.
Complaints 23 (20 first-hand reports, 3 with data or benchmarks) vs counter-evidence 5 vs official responses 2 (both status-page outage incidents on Nov 13, none about model quality). Plus 4 workarounds.
Comments