Repository navigation
README: semantic_query is not a tool, the tool count is 14 not 15, and the team artifact is not written by default #1297
Description
Activity
- addedcypherCypher query language parser/executor bugsCypher query language parser/executor bugseditor/integrationEditor compatibility and CLI integrationEditor compatibility and CLI integrationparsing/qualityGraph extraction bugs, false positives, missing edgesGraph extraction bugs, false positives, missing edges
on Jul 27, 2026 - addedbugSomething isn't workingSomething isn't workingdocumentationImprovements or additions to documentationImprovements or additions to documentationpriority/normalStandard review queue; useful PR with ordinary maintainer urgency.Standard review queue; useful PR with ordinary maintainer urgency.
on Jul 28, 2026 Thanks for checking the README against the actual server rather than relying on the prose.
The contradictions remain code-grounded on current main: semantic_query is a search_graph parameter in the tool schema (src/mcp/mcp.c:381-416), and persistence is explicitly default false (src/mcp/mcp.c:376). The server advertises the TOOLS array beginning at src/mcp/mcp.c:347, not a standalone semantic_query tool.
PR #1315 is now linked to this documentation bug and is queued for review. I have routed the issue to 0.9.1-rc at priority/normal; that routing does not pre-approve the PR. Thank you for grouping the four concrete claims in one reproducible report.
Also, the readme mentions
trace_call_path, which is actually calledtrace_path.And there's an undocumented
check_index_coveragetool as well.Maybe ask your agent to check if the documentation matches the codebase? 😊
- addedpriority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.Needs near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.and removedpriority/normalStandard review queue; useful PR with ordinary maintainer urgency.Standard review queue; useful PR with ordinary maintainer urgency.
on Sep 5, 2026 - added a commit that references this issue
on Sep 22, 2026 - added 2 commits that reference this issue
on Sep 29, 2026 - added a commit that references this issue
on Sep 30, 2026 - added a commit that references this issue
on Sep 30, 2026 Thank you again for reporting this, @melihemreguler! The fix is now on
mainin 39da5de (merged via #2403), and it will ship in the next release.
1.
semantic_queryis presented as a tool but is a parameterThe Search section introduces
semantic_queryas though it were an MCP tool. It is not:semantic_queryexists only as a parameter ofsearch_graph. The README's own MCP Tools table does not list it, so the two sections contradict each other.2. Tool count is 14, not 15
The intro and the Manual MCP Configuration section both state 15 tools ("you should see
codebase-memory-mcpwith 15 tools"). The server advertises 14 viatools/list(paginated: 8 withnextCursor: 8, then 6).3. The team-shared artifact is opt-in, not automatic
Team-Shared Graph Artifact says:
In practice
persistencedefaults tofalse(src/mcp/mcp.c:376), soindex_repositoryreportsartifact_present: falseand no.codebase-memory/graph.db.zstis created unlesspersistence: trueis passed explicitly.4. The dead-code Cypher example is rejected by the engine
Supported Cypher offers
WHERE NOT EXISTS { (f)<-[:CALLS]-() }as the dead-code example. The engine rejects the inbound form. See #1293.Environment