Claude Code is being dumbed down?

What Actually Changed in Claude Code’s UX

• The CLI now summarizes actions as “Read 3 files / Searched for 1 pattern (ctrl+o to expand)” instead of listing exact paths and grep patterns inline.
• This information is still available via verbose mode and ctrl+o, but no longer visible at-a-glance in the default view.
• Several users report longer “thinking” phases, many more tool calls, and difficulty understanding what the agent is doing while burning tokens.

Power Users vs “Vibe Coders”

• Many developers see this as catering to “vibe coders” and non‑technical users who just want “make a website, don’t make mistakes,” with minimal logs.
• Others argue that experienced engineers need to see what’s being read to catch wrong assumptions (e.g., wrong module, stale docs) and interrupt early.
• A minority say they like the cleaner output and don’t care what was read as long as the diff looks good.

Transparency, Observability, and Security

• Several comments frame this as an observability problem: agentic tools need a minimum audit trail (which files, which searches) to be safe to use on real codebases.
• Some worry that removing file paths hides potential data exfiltration (e.g., SSH keys, sensitive files) and reduces ability to notice prompt‑injection‑driven behavior.
• Screen‑reader users say the change is an accessibility regression: they now must choose between “no info” and overwhelming verbose output.

Perceived Degradation, Tokens, and Business Model

• Multiple users report sessions that spin for minutes, thrash across many files and tools, or appear “dumber” or more circular since 4.6, though others strongly contest broad “degradation” claims.
• Suspicion appears that opaque behavior plus per‑token billing incentivizes unnecessary tool use; others attribute the behavior to immature agent loops and compaction issues.

Alternatives, Lock‑In, and Standards

• Many mention moving or experimenting with alternatives: OpenCode, Codex CLI, Cursor, Gemini CLI, self‑hosted tools like pi, RooCode, etc.
• Frustration is high that Anthropic blocks or discourages third‑party harnesses with subscription plans, keeps the CLI closed/minified, and does not support the AGENTS.md “standard”.

Product Management, Configuration, and Enshittification Fears

• Long subthreads debate product management: is this legitimate simplification for the median user, or classic “enshittification” and top‑down dumbing down?
• Strong calls for fine‑grained, Unix‑style verbosity controls (multiple levels, per‑signal toggles) instead of one “verbose mode” that changed semantics mid‑stream.
• Some see this as emblematic of VC‑backed AI tools sliding from hacker‑friendly to mass‑market, with reduced transparency and user control over time.

Anthropic’s In‑Thread Explanation

• A Claude Code team member explains: models now run much longer agentic trajectories, flooding small terminals with output; the change was aimed at reducing noise via “progressive disclosure,” dogfooded internally and preferred by “most users.”
• They acknowledge missing the mark for a subset of users, say verbose mode was repurposed to show explicit file paths without full thinking traces, and promise further tweaks (e.g., better subagent output, improved ctrl+o behavior).
• Critics counter that repurposing verbose mode broke existing workflows and that a simple config flag for showing file paths inline would have avoided most backlash.