Debugging Claude Code's Build-Check Logic: Why Name Search Fails and Structural Footprint Search Fixes It

A developer on r/ClaudeAI reports that Claude Code repeatedly failed to detect existing features, claiming “is X built?” returned “no” four times in a single session — each time the feature already existed. The root cause: the agent searched by name (keywords, synonyms) instead of by structural footprint (routes, schemas, registered tools, scheduled jobs, documented decisions). Names drift; architectural artifacts don’t.
The pattern
Asking “is this feature already built?” triggered a confident “no, here’s how we’d build it,” even when the feature was partially implemented. Each time the user had to push back to extract the real answer. The developer diagnosed that the agent was searching, but using vocabulary-based queries that missed code with different naming conventions.
The rule (structural footprint search)
The synthesized rule forces the agent to search by shape, not name. For example, instead of “find feature X,” it asks “what plugin tools exist?” or “what routes, schemas, or registered jobs match this functionality?” This catches prior code that a name search never would have matched.
Key shift: “Searching by better synonyms is still searching by name. The footprint version catches it (the prior code registered a plugin tool, and ‘what plugin tools exist?’ is a high-signal narrow search).”
Requested feedback from the community
- Hallucination shapes structural footprint search would NOT catch
- Audit-theater patterns where the form is satisfied without substance
- Over-triggering on questions that aren’t actually absence claims
- Confidence amplification: post-audit, agent more confident in conclusions, making wrong-ontology errors harder to catch
- Wrong-ontology rigor: agent searches GraphQL patterns on a REST system, finds nothing, confirms absence
The developer is testing the rule in a separate project for 2–3 weeks before considering a global config. They invite others to share rules that solved “hallucination with rigor” (not just hallucination).
📖 Read the full source: r/ClaudeAI
👀 See Also

Developer shares CLI tools that work well with Claude Code
A developer switched from MCPs to CLIs for working with Claude Code, finding that Claude handles CLI commands effectively due to training on shell scripts and documentation. They shared specific CLIs they use daily, including gh, ripgrep, stripe, supabase, vercel, sentry-cli, and neon.

Recursive Self-Improvement Framework for AI Coding Agents Using Claude Code
An open-source framework enables AI coding agents to recursively improve themselves using Claude Code. The system analyzes agent traces, identifies failure patterns, and implements fixes, achieving a 25% performance increase in one test cycle.

Natural Language Autoencoders: Turning Claude's Internal Representations into Text
Transformer Circuits Thread publishes Natural Language Autoencoders that decode Claude's internal activations into readable text. GitHub repo and interactive demo available.

Relay: Open-Source Control Plane for OpenClaw AI Agents
Relay is an Electron desktop app that provides Claude Cowork-like workflow for OpenClaw, running on your infrastructure with your choice of LLM models and built-in governance features including approval gates and exportable audit trails.