Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Skip to main content
The direction flags are mutually exclusive.
These examples use the tutorial project. In another repository, use its actual labels or IDs.
graphify path
[Local] Trace the shortest relationship path between two graph concepts.
graphify path "<source>" "<target>" [--graph <path>] [--directed | --undirected]
| Argument | Meaning |
|---|---|
| Source and target | Node labels, IDs, or matching keywords. |
--graph | Use a specific JSON graph. |
--directed | Respect stored direction; this is the current default. |
--undirected | Explore connectivity while ignoring direction. |
graphify path "login" "normalize_email"
graphify path "normalize_email" "login" --undirected
Interpret the path
Follow each relationship and check its evidence. A source-level path does not prove that a particular runtime input executes it. An absent path can mean missing or unresolved relationships; it does not prove independence. For the MCP version, useshortest_path. Its inputs additionally expose max_hops; see the MCP reference.
Assistant
Responses are generated using AI and may contain mistakes.