Skip to main content
GSD Graph stores relationships from your documentation and planning files as subject–predicate–object triples with source provenance. You can follow dependency chains, inspect decisions, and answer questions from a focused subgraph. The default extraction and answer paths run locally without an API key. Optional LLM stages add prose extraction and grounded answers. GSD Graph runs independently of GSD Core, GSD Path, and Python graphify.

Build your first graph

Install the CLI and ask a question about an explicit relationship chain.

Use the graph each day

Keep your graph current and choose between ask, query, pack, and why.

Connect your agent

Register the MCP server and choose which write tools to enable.

Prepare your corpus

Learn what gets indexed and how prose becomes relationships.

​
How it works

The canonical store is .gsd-graph/graph.v1.json. Queries retrieve relevant nodes, triples, paths, and citations. Answers use this evidence and can abstain when there is no supporting subgraph. Use GSD Graph for relationships in project knowledge. For source-code callers, imports, and change impact, use a code graph tool. GSD Graph does not scan all of src/ by default. See the source repository and release history.