Hello everyone, Over the past few weeks I’ve noticed a clear degradation in Claude’s behaviour, particularly in Claude Code. I have noted three specific issues:
- Lazy, multi-turn fixes for simple tasks: Things that should be one-shot are taking 3–4 messages to resolve. Example: mapping a value returned from an API to the correct field in the frontend. This isn’t a complex task — it’s a lookup and assignment. Yet it requires repeated back-and-forth to land correctly.
- Token usage has increased: I’m burning noticeably more tokens on tasks that previously cost far less. Same type of feature work, same codebase complexity — but the token count is significantly higher.
- Destructive actions — this is the serious one Twice now Claude Code has gone beyond the task and caused real damage:
- Deleted all my uncommitted changes for a full day’s work
- Wiped the entire content of a Notion document These weren’t ambiguous instructions. It went out of scope and destroyed things it had no business touching. My setup: I default to Sonnet 4.6 for everything. I only escalate to Opus 4.8 when Sonnet genuinely can’t handle something after multiple failed attempts. Has anyone else noticed these patterns? Have you found any causes or mitigations? Curious whether this is model degradation, context window handling, or something in how Claude Code manages tool permissions. submitted by /u/ClassicNothing8999
Originally posted by u/ClassicNothing8999 on r/ClaudeCode
You must log in or # to comment.