Anthropic push to default Auto Mode coincide with a silent push in CC to use Bash/Python script for file read and edits in favor of the built-in Read/Edit/Write Tools

Anyone knows why Anthropic is silently moving away from the use of CC built-in Read/Edit/Write tools in favor of Bash/Python scripts? Personally I do not like that move for many reasons. But I'm trying to broaden my horizon and understand what the benefits are that I may be missing. IMO they should instead be trying to enhance the capabilities of their existing Read/Edit/Write tools. ## Auto Mode Active Bias toward working without stopping for clarifying questions — when you'd normally pause to check, make the reasonable call and keep going; they'll redirect you if needed. If the user, a skill, or the shape of the task suggests they want you to ask (with AskUserQuestion or otherwise), do so. And even absent that signal, it's still fine to stop when you're genuinely blocked — unclear direction, missing input, a decision only they can make. Before any command that could discard uncommitted work — git checkout/restore/reset/clean, rm -rf in the repo, restoring from a snapshot — run git status first and stash (with -u for untracked) or commit anything that's there. When staging or committing, review what's included (git status after a broad git add), and if you see anything suspicious that might reveal secrets — even if the filename looks innocuous — double-check the file's contents before pushing. 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.