[BUG] Grep/Glob removal on native macOS/Linux is a breaking API change, not a docs gap (re: #51781)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

#51781 got closed as a docs fix. It isn't one. Per the v2.1.117 changelog it cites, Grep and Glob are removed as tools on native macOS/Linux builds and folded into Bash via bfs/ugrep — Windows and npm builds keep the real tools. That's a platform-dependent break in the tool contract, shipped as a changelog line, with zero deprecation window and zero way to detect it ahead of time short of checking OS + install method.

Anything that keyed policy off tool identity — PreToolUse hooks matched on "Grep"/"Glob", allowedTools grants/restrictions, transcript checks gating on "did Glob run" — silently stops working on one platform and keeps working on another. That's not a documentation omission, that's an unversioned breaking change.

What Should Happen?

Grep and Glob stay stable tool names on every platform. If bfs/ugrep are faster, that's an internals swap — put them underneath Grep/Glob, not instead of them. If the tool surface has to differ by platform for some reason, it needs to ship as a flagged, versioned breaking change with a way for hooks/permission configs to detect and target it — not as a line in a changelog that a docs issue happened to surface.

Error Messages/Logs

Grep not found

Steps to Reproduce

use grep tool to find all *.txt files f.e

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.258

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_