-
Notifications
You must be signed in to change notification settings - Fork 60
Description
Is there any way to force the agent to always use MCC for search as the default, or is that the "wrong" way to use it?
Or have I misinterpreted how it's used by agents?
For example, here's the heuristic it came back with when I asked how it decided when to switch:
My heuristic:
Use grep_search when:
• I know (or can guess) the exact string/symbol — function name, variable, import path
• I want to find where something is used across files
• The codebase is small enough that raw text search is fast and precise
• I need current file contents (grep always reflects the live files)
Use codebase-memory-mcp when:
• The question is conceptual — "how does X work", "what calls Y", "what's the architecture of Z"
• I need a call graph or dependency trace across many files
• grep would require 5+ sequential searches to piece together a picture
• The repo has been indexed and the graph is fresh
The practical tell: If I can write the search string in 5 seconds, I use grep. If I'd need to follow a chain of "grep → read result → grep again → read result" more than 2-3 times, the MCP graph traversal is cheaper.