1. Silent Performance Degradation
Users repeatedly noticed drops in model quality—such as stripped thinking tokens, altered defaults, and reduced verbosity—without any announcement.
"They changed the default in March from high to medium, however Claude Code still showed high (took 1 month 3 days to notice and remediate). Old sessions had the thinking tokens stripped, resuming the session made Claude stupid (took 15 days to notice and remediate)." – jryio
2. Lack of Transparency and Communication
Anthropic’s failure to inform users about changes led to feelings of being misled or “gaslit,” especially when they claimed no performance degradation while making impactful adjustments.
"the experience of suspecting a model is getting worse while Anthropic publicly gaslights their user-base: 'we never degrade model performance' is frustrating." – jryio
3. Trust Erosion and Shift to Alternatives
Many users expressed lost confidence and began experimenting with or switching to other models like Codex, Gemini, or MiniMax due to unreliability.
"I went with MiniMax. The token plans are over what I currently need, 4500 messages per 5h, 45000 messages per week for 40$." – simlevesque
4. Caching and Session Resumption Issues
The automatic clearing of thinking tokens after idle periods (and related bugs) caused sessions to lose context, forcing users to rebuild work or face unexpected token costs.
"after a one hour user pause, apparently they cleared the cache and then continued to apply 'forgetting' for the rest of the session after the resume!" – fn-mote
5. Unexpected Token Usage and Cost Concerns
Sudden cache misses triggered large token consumption, quickly exhausting usage limits and creating anxiety over unpredictable costs.
"I was running the exact same pipeline… and yet this time I somehow ate a week’s worth of quota in less than 24h. I spent $400 just to finish the pipeline pass that got stuck halfway through." – frumplestlatz
6. Comparison to Competing Models
Users frequently contrasted Claude with alternatives—particularly Codex—citing better reliability, transparency, or tool integration.
"I know many people who have supplemented Claude with Codex, and are experimenting with models such as GLM 5.1, Kimi, Qwen, etc." – bensyverson
7. Critique of Rapid Deployment / Vibe‑Coding Culture
The pattern of frequent, poorly tested changes was attributed to a “move fast and break things” mindset that prioritized speed over stability.
"It's clear they are playing with too many independent variables simultaneously." – jryio
"this is the quality of software you get atm when your org is all in on vibe coding everything." – Eridrus