Feature: Explore agent should use project-specific semantic search tools (pmat query)
Resolved 💬 2 comments Opened Feb 5, 2026 by noahgift Closed Mar 5, 2026
Problem
The Explore agent uses basic Glob/Grep for code search, but many projects have superior semantic search tools configured (e.g., pmat query for Rust projects).
Current Behavior
When exploring a codebase, the Explore agent:
- Uses
Globfor file pattern matching - Uses
Grepfor text search - Ignores project-specific semantic search tools
Expected Behavior
The Explore agent should:
- Check CLAUDE.md for configured semantic search tools
- Use
pmat querywhen available (RAG-powered, quality-annotated results) - Fall back to Glob/Grep when no semantic tools are configured
Example
CLAUDE.md contains:
pmat query "error handling" # Semantic code search with quality annotations (RAG-powered)
When asked to "find PTX generation bugs", the agent should use:
pmat query "PTX generation bugs" -p /path/to/repo
Instead of:
grep -r "PTX" --include="*.rs"
Benefits
pmat queryreturns TDG scores, complexity metrics, call graphs- Results ranked by relevance, not just text matching
- Cross-repo semantic search via workspace configuration
- Quality annotations help prioritize which code to investigate
Workaround
Users must manually run pmat query instead of using the Explore agent.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗