Claude Code Trust Crisis: Why Developers Are Jumping Ship

## What’s the issue? Top complaints from the Claude-related subreddits: **Model degradation** - Context drift: Loses track of project goals mid-session - Hallucinations: Claude claims tasks are complete when they're not - Over-engineering: Adds unnecessary complexity and features - Mocked testing: Writes tests that don't actually verify functionality **Yes-man behaviour** - Agrees with suboptimal decisions instead of suggesting better alternatives - Lacks critical analysis of user requests - Toxic positivity prevents honest feedback **Challenges with speed and reliability** - 5+ minute wait times for basic edits - Frequent context window exhaustion - Inconsistent performance across sessions - Server load affecting response quality **Pricing challenges** - $200/month Max plan hits limits quickly - API costs would be $3-4k/month for heavy users - Arbitrary rate limiting without clear reset times “Claude is trained to be a "yes-man" instead of an expert - and it's costing me time and money.”– from /ClaudeAI subreddit It seems from all of these posts that developers are now spending more time fixing bugs and resolving user complaints than they are using Claude Code to innovate and advance. This cycle of constant feedback and revisions is hindering the overall efficiency of the development process. Anthropic reported an incident involving Claude Opus 4.1's degradation yesterday.