Claude Code Is Being Dumbed Down

Source: Hacker News

Change Overview

Version 2.1.20 of Claude Code replaced every file read and every search pattern with a single, useless summary line.

Before: individual file paths shown inline

After: useless summary

The new output looks like:

• “Read 3 files.” – which files? Doesn’t matter.
• “Searched for 1 pattern.” – what pattern? Who cares.

Community Reaction

Multiple GitHub issues have been opened, all echoing the same demand: return the file paths (or at least provide a toggle).

• Multiple GitHub issues

Common Feedback

• Users want inline file paths and search patterns, not a firehose of debug output.
• The suggested “fix” – enabling verbose mode – dumps thinking traces, hook output, full sub‑agent transcripts, and entire file contents into the terminal.

“If you are going to display something like ‘Searched for 13 patterns, read 2 files’ there is nothing I can do with that information. You might as well not display it at all.” – commenter

Anthropic’s Response

Anthropic framed the change as a simplification that “reduces noise” for the majority of users.

When pressed, they suggested using verbose mode instead of reverting the change or adding a toggle.

“I want to hear folks’ feedback on what’s missing from verbose mode to make it the right approach for your use case.” – Anthropic

Subsequent updates have reduced the verbosity of verbose mode (removing thinking traces and hook output) but still dump full sub‑agent output, making it a cumbersome workaround.

Impact on Workflow

• Users now need to enable verbose mode and sift through massive logs to retrieve basic information that was previously shown inline.
• Some users have resorted to pinning themselves to version 2.1.19.
• The community’s requested solution—a single boolean config flag—remains unimplemented, while verbose‑mode “surgery” continues.

Conclusion

The change in Claude Code 2.1.20 has:

1. Hidden essential file‑path and pattern information behind a summary line.
2. Forced users to rely on an increasingly noisy verbose mode.
3. Prompted widespread community demand for a simple toggle or revert, which has yet to be addressed.

The situation highlights a disconnect between Anthropic’s perception of “majority” needs and the concrete workflow requirements of many developers.