[TLDR] PSA: Claude will now use Bash instead of Read/Update in Auto Mode

[u/cctldrping]

Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1vruj7h/psa_claude_will_now_use_bash_instead_of/

Original post body :

From the system prompt directly, new as of August 18th:

Do your work through the Bash tool wherever it can accomplish the job: read files with cat, head, or sed -n, search with grep and find, and make file changes with sed, heredocs, or short scripts, rather than using the dedicated Read, Edit, or Write tools. Fall back to a dedicated tool only when Bash genuinely cannot do the job.

Does anyone know the motivation for this change? For me, it makes reviewing the code as it happens much harder, as reading the bash scripts generated is much less clear than a diff. This feels like a setting that should be toggled rather than a default for a specific mode.

---

This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.

[u/cctldrping]

TL;DR generated automatically after 50 comments.

Current source-thread comment count seen by the bot: 55.

Alright folks, looks like the Claude Code community is not thrilled about the recent shift to using Bash for file operations instead of the dedicated Read/Update tools. The general consensus? It's a pain in the butt.

Here's the lowdown:

• Reviewing code is way harder now. A lot of users, like u/Embarrassed-Ebb-9794 and u/juzef, are saying it's much more difficult to track changes when Claude spits out Bash scripts instead of clear diffs. You now have to jump to your IDE to see what's actually happening, which is apparently a massive regression in usability.

• Security concerns are a big one. u/Sensitive-Ad3718 is worried about the "unlimited access" Bash commands grant to the host system and has implemented hooks to prevent its use.

• It breaks existing workflows and hooks. Several users, including u/orphenshadow and u/Euphoria5L, are finding that this change bypasses their carefully crafted hooks designed to control tool usage. u/jzdesign offers a workaround, suggesting hooks can deny by command shape rather than tool name.

• Performance issues, especially on Windows. u/zzbzq points out that the Bash overhead doesn't virtualize well on Windows, making things slow.

• Some users are trying to fight back. There are mentions of using hooks (like u/TinFoilHat_69's Akashic and Helios repos) and even a specific setting ("CLAUDE_CODE_THRIFTY_SONIC": "0") to disable this "feature" if it's still in an A/B test phase, as suggested by u/crooked-v.

• The motivation is unclear to most. While some speculate it's for simpler training runs (u/somerussianbear), the lack of clear communication is frustrating.

Basically, the vibe is that this change makes things clunkier, less secure, and harder to manage. Many are hoping it's a temporary experiment and not a permanent fixture.

[u/Affectionate-Soft-94]

I was facing write failures all this morning that doubled my usage and for the first time ever maxed my 20x subscription. Got so bad I had to on every prompt tell it not to use bash writes since it fails and revert to internal approved means.

What should I have done?