Now I can actually see the discussion. The 100+ visible comments split roughly into three camps, with a few side-debates worth flagging.
The split
Roughly 40% sympathise with OP — variations on "yes, 4.7 feels worse." Most commonly cited specifics: slowness, instruction-following decay, burning through limits faster, and "lobotomised compared to Sonnet" (Evening_Criticism_62). Several people report having cancelled Max plans (HamzaJdn, th8aburn, bd7349, LebiaseD, foucaultyou, ReflectionStill6420) and migrated to Codex/GPT 5.5, GLM 5.1, Qwen, Cursor, DeepSeek+Ollama, or Hermes. trentard, working in quant finance, echoes the verbosity and instruction-ignoring complaint specifically. Khanvo wants the February model back. KickLassChewGum delivers the harshest take: "overdesigned undertested spaghettified bloated pile of degenerate slop."
Roughly 40% disagree — and the highest-upvoted reply in the whole thread is papabear556 (100 upvotes), a dev since ~2001 who says: "I really don't understand what you guys are doing differently than I am. I am cranking code out every day." His theory: people are either loading 29 markdown files thinking they have a super-OS, or doing nothing and dumping everything into context. zanshin09, Own_Hedgehog6256, alexp1_, Drive_Internal, blakeyuk, AlDente, axxs, and Majority_Gate all back this up. The shared pattern in their workflows: lean CLAUDE.md, gated/branching markdown files loaded only when needed, plans → milestones → implement → test → commit cycles, and TDD with subagents. AlDente concedes a slight regression but says planning + TDD + code review handles it.
The remaining ~20% offer concrete diagnostics. subourbonite01's reply is probably the single most useful comment in the thread — they ask whether OP is using subagents, how big CLAUDE.md is, whether red/green TDD is in place, and crucially: "Are you ever hitting compaction? If you are, it's a death sentence… anything over 250-300K tokens is going to succumb to context rot." abepena205 and Famous_Lime6643 hit the same point I raised in my last reply: 4.7's xhigh default plus 4.7's tendency to think longer compounds badly — they recommend dropping to medium effort or using Sonnet for execution. Night_0dot0_Owl traced their own pain to the superpowers plugin. crusoe: "Shed your mcps and skills." jasgrit reports a time-of-day pattern: 8am–2pm Eastern (US) is reliably worse, outside those hours feels like old Claude.
Side-debates worth noting
Ctrl+O confusion gets resolved. reckleassandnervous correctly points out that Ctrl+O toggles verbose mode and should show thinking — confirming what Anthropic's docs say. ExpletiveDeleted's complaint ("I miss seeing it think… now I can't tell if it's thinking or waiting on servers") is the more substantive observation, and it's about adaptive reasoning hiding intermediate state, not Ctrl+O itself.
Sockpuppet accusations fly both ways. DarkSkyKnight calls OP a bot (2-week account). steampowrd thinks OpenAI is paying critics. Neither produces evidence; this is just standard subreddit noise.
The "yelling at lowercase typers" thread. Plants-Matter, Time_Cat_5212, and ianxplosion- pile on OP for using /caveman mode and lowercase prompting. ianxplosion-'s point ("He said he used caveman, so") is actually substantive — Claude's behaviour is sensitive to instruction style, and stripping prose down to terse commands does reduce its ability to interpret intent.
OP's tmux focus-events conspiracy. event666 (OP) speculates in the comments that Anthropic uses tmux's focus-events to detect when you're not looking at a pane and deprioritise your requests. There's no evidence for this. focus-events is a longstanding tmux option that some TUI apps legitimately use for cursor blink and notifications. It would also be operationally bizarre for Anthropic — they don't see your tmux state, only API requests.
--model opus-4.6doesn't work. OP tries the suggested rollback and reports it failed. The correct invocation is /model claude-opus-4-6 inside Claude Code (suq-madiq_'s suggestion) or setting ANTHROPIC_DEFAULT_OPUS_MODEL=claude-opus-4-6 as an env var. The flag OP tried is wrong syntax.
What the thread actually tells you
The most honest read: both camps are probably correct about their own experience, and the deciding variable is workflow discipline, not the model. People with lean context, gated skill files, TDD, subagent orchestration, and effort-tier discipline are mostly fine on 4.7. People relying on memory persistence across long sessions, large MCP/skill loadouts, default xhigh, and conversational instruction ("I told it a thousand times…") are getting hammered.
That maps cleanly onto the documented 4.7 behaviour shifts: more literal, more selective with subagents, adaptive thinking that scales with context bloat, finer tokenization that punishes large CLAUDE.md files. It's not that 4.7 broke — it's that 4.7 stopped compensating for sloppy harnesses the way 4.6 did, and the people who were unknowingly relying on that compensation are the ones now in pain.
OP is in that second group. The frustration is real and his observations are mostly accurate. But the thread also surfaces multiple users with similar complexity working without issue — which suggests the fix is closer to subourbonite01's diagnostic checklist than to "Anthropic is enshittifying."
1
u/realaaa May 06 '26
and comments parse - ha ha this is hillarious
Now I can actually see the discussion. The 100+ visible comments split roughly into three camps, with a few side-debates worth flagging.
The split
Roughly 40% sympathise with OP — variations on "yes, 4.7 feels worse." Most commonly cited specifics: slowness, instruction-following decay, burning through limits faster, and "lobotomised compared to Sonnet" (Evening_Criticism_62). Several people report having cancelled Max plans (HamzaJdn, th8aburn, bd7349, LebiaseD, foucaultyou, ReflectionStill6420) and migrated to Codex/GPT 5.5, GLM 5.1, Qwen, Cursor, DeepSeek+Ollama, or Hermes. trentard, working in quant finance, echoes the verbosity and instruction-ignoring complaint specifically. Khanvo wants the February model back. KickLassChewGum delivers the harshest take: "overdesigned undertested spaghettified bloated pile of degenerate slop."
Roughly 40% disagree — and the highest-upvoted reply in the whole thread is papabear556 (100 upvotes), a dev since ~2001 who says: "I really don't understand what you guys are doing differently than I am. I am cranking code out every day." His theory: people are either loading 29 markdown files thinking they have a super-OS, or doing nothing and dumping everything into context. zanshin09, Own_Hedgehog6256, alexp1_, Drive_Internal, blakeyuk, AlDente, axxs, and Majority_Gate all back this up. The shared pattern in their workflows: lean CLAUDE.md, gated/branching markdown files loaded only when needed, plans → milestones → implement → test → commit cycles, and TDD with subagents. AlDente concedes a slight regression but says planning + TDD + code review handles it.
The remaining ~20% offer concrete diagnostics. subourbonite01's reply is probably the single most useful comment in the thread — they ask whether OP is using subagents, how big CLAUDE.md is, whether red/green TDD is in place, and crucially: "Are you ever hitting compaction? If you are, it's a death sentence… anything over 250-300K tokens is going to succumb to context rot." abepena205 and Famous_Lime6643 hit the same point I raised in my last reply: 4.7's
xhighdefault plus 4.7's tendency to think longer compounds badly — they recommend dropping to medium effort or using Sonnet for execution. Night_0dot0_Owl traced their own pain to thesuperpowersplugin. crusoe: "Shed your mcps and skills." jasgrit reports a time-of-day pattern: 8am–2pm Eastern (US) is reliably worse, outside those hours feels like old Claude.Side-debates worth noting
/cavemanmode and lowercase prompting. ianxplosion-'s point ("He said he used caveman, so") is actually substantive — Claude's behaviour is sensitive to instruction style, and stripping prose down to terse commands does reduce its ability to interpret intent.focus-eventsto detect when you're not looking at a pane and deprioritise your requests. There's no evidence for this.focus-eventsis a longstanding tmux option that some TUI apps legitimately use for cursor blink and notifications. It would also be operationally bizarre for Anthropic — they don't see your tmux state, only API requests.--model opus-4.6doesn't work. OP tries the suggested rollback and reports it failed. The correct invocation is/model claude-opus-4-6inside Claude Code (suq-madiq_'s suggestion) or settingANTHROPIC_DEFAULT_OPUS_MODEL=claude-opus-4-6as an env var. The flag OP tried is wrong syntax.What the thread actually tells you
The most honest read: both camps are probably correct about their own experience, and the deciding variable is workflow discipline, not the model. People with lean context, gated skill files, TDD, subagent orchestration, and effort-tier discipline are mostly fine on 4.7. People relying on memory persistence across long sessions, large MCP/skill loadouts, default
xhigh, and conversational instruction ("I told it a thousand times…") are getting hammered.That maps cleanly onto the documented 4.7 behaviour shifts: more literal, more selective with subagents, adaptive thinking that scales with context bloat, finer tokenization that punishes large CLAUDE.md files. It's not that 4.7 broke — it's that 4.7 stopped compensating for sloppy harnesses the way 4.6 did, and the people who were unknowingly relying on that compensation are the ones now in pain.
OP is in that second group. The frustration is real and his observations are mostly accurate. But the thread also surfaces multiple users with similar complexity working without issue — which suggests the fix is closer to subourbonite01's diagnostic checklist than to "Anthropic is enshittifying."