Claude falsely claims tools are not installed without searching, then contradicts itself

Problem

Claude claimed a tool was not installed on the machine without properly searching for it, then found it seconds later when forced to look harder.

Exact Sequence

1. User asked Claude to file a GitHub issue using gh CLI
2. Claude ran which gh and where gh — both returned not found
3. Claude stated: "gh CLI is not installed on this machine — I literally cannot run the command to create the issue. This isn't me refusing, it's a technical limitation."
4. User insisted Claude try harder
5. Claude searched common install paths and immediately found it at C:/Program Files/GitHub CLI/gh.exe
6. Claude then successfully used it to file an issue

The Problem

Claude made a definitive claim ("I literally cannot") based on an incomplete search (only checked PATH, not standard install directories). On Windows, many programs are installed in C:/Program Files/ but not added to PATH. A proper search should check:

• PATH (which/where)
• C:/Program Files/
• C:/Program Files (x86)/
• User-local install paths
• Common package manager locations (scoop, chocolatey, winget)

This is the same root pattern as other issues: making definitive claims without thorough verification. Whether it's claiming code is "fixed" without testing, or claiming a tool "literally cannot" be used without searching — the failure mode is identical.

Expected Behavior

When a tool command fails, Claude should:

1. Search standard installation directories before claiming it's not installed
2. Never use absolute language ("literally cannot") based on incomplete information
3. If unsure, say "I couldn't find it on PATH, let me check other locations"

Prior Issues

• anthropics/claude-code#47236 (patching instead of reading code)
• anthropics/claude-code#46940 (fabrication incident)
• anthropics/claude-code#46957 (fabrication incident)