You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Normalize `codegraph_files``path` filters to root-relative POSIX prefixes and append a deterministic hint when no files match, preventing agents from concluding a directory does not exist. Fixes #40.
Remove `codegraph_context` and `codegraph_trace` tools, which upstream CodeGraph dropped in v0.9.9+, and update guidance to use `codegraph_explore` instead. Fixes #37.
Copy file name to clipboardExpand all lines: README.md
+2-6Lines changed: 2 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@
8
8
9
9
Ask pi structural questions about your codebase without falling back to slow grep/read loops.
10
10
11
-
An extension for [pi](https://pi.dev) that gives the agent access to [CodeGraph](https://github.com/colbymchenry/codegraph) tools. CodeGraph indexes your project with tree-sitter, then pi can query symbols, callers, callees, dependency impact, files, and call paths through native extension tools.
11
+
An extension for [pi](https://pi.dev) that gives the agent access to [CodeGraph](https://github.com/colbymchenry/codegraph) tools. CodeGraph indexes your project with tree-sitter, then pi can query symbols, callers, callees, dependency impact, files, and relationships through native extension tools.
12
12
13
13
---
14
14
@@ -36,13 +36,11 @@ Extension tools only. There is no MCP setup for pi users to maintain.
36
36
37
37
| Tool | Description |
38
38
| --- | --- |
39
-
|`codegraph_context`| Broad task context: entry points, related symbols, callers, callees, and key code |
40
39
|`codegraph_search`| Symbol search by name |
41
40
|`codegraph_node`| One symbol's signature, location, source, callers, and callees |
42
41
|`codegraph_files`| Indexed file tree |
43
42
|`codegraph_callers`| Functions or methods that call a symbol |
44
43
|`codegraph_callees`| Functions or methods called by a symbol |
45
-
|`codegraph_trace`| Static call path from one symbol to another |
46
44
|`codegraph_impact`| Impact radius for changing a symbol |
47
45
|`codegraph_explore`| Source for several related symbols grouped by file |
48
46
|`codegraph_status`| Index health and pending sync status |
@@ -126,12 +124,10 @@ Use CodeGraph. Show files under internal/services and important symbols.
126
124
127
125
### 3. Prefer the right tool
128
126
129
-
Use `codegraph_context` for broad "how does this work?" questions.
127
+
Use `codegraph_explore` for broad "how does this work?" or "how does X reach Y?" questions.
130
128
131
129
Use `codegraph_node` when you already know the symbol name.
132
130
133
-
Use `codegraph_trace` for "how does X reach Y?" flow questions.
134
-
135
131
Use `codegraph_search` for declarations and symbols, not arbitrary text or constant values.
return`${resultText}\n\nHint: codegraph_files interprets "path" as a root-relative POSIX prefix (e.g. "src/components"). The filter "${originalPath}" did not match any indexed path.`;
"CodeGraph tools are available as codegraph_* Pi tools.",
361
395
"For architecture, flow, where-is-symbol, impact, and codebase navigation questions, use CodeGraph tools directly before grep/read.",
362
-
"Use codegraph_context first for broad questions, codegraph_search for symbol-name lookup, codegraph_files for project structure, codegraph_node for a known symbol, and codegraph_trace for call paths.",
363
-
"If codegraph_search returns no exact result, try codegraph_context or codegraph_files/codegraph_explore before falling back to grep/read; CodeGraph symbol search may miss literal constants or generated names that still exist in source text.",
396
+
"Use codegraph_explore first for broad questions, codegraph_search for symbol-name lookup, codegraph_files for project structure, codegraph_node for a known symbol, and codegraph_callers for impact/flow analysis.",
397
+
"If codegraph_search returns no exact result, try codegraph_explore or codegraph_files/codegraph_node before falling back to grep/read; CodeGraph symbol search may miss literal constants or generated names that still exist in source text.",
364
398
"Only use grep/read after CodeGraph is insufficient or when the user asks for literal text matching.",
0 commit comments