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
Your first knowledge graph
[Local] Install Graphify, map your repository, and ask a question about your code.
Graphify turns a repository into a graph of its functions, classes, imports, and relationships. Your assistant can query that graph instead of repeatedly scanning the same files.
This quickstart uses the open-source engine on your machine. You need Python 3.10 or later and a supported coding assistant. For the hosted product, see Graphify Cloud.
This installs the Graphify skill for a detected assistant. To choose one explicitly:See all integrations for your assistant’s setup.Open
If you are an agent, read Notes for agents before these steps.
Install the CLI
Stay on one tab. The version check is the same either way.
uv tool install graphifyy
graphify --version
pipx install graphifyy
graphify --version
graphify --version prints the version you installed. The latest release is on PyPI and in the changelog. The package is graphifyy, with two y’s. The command is graphify. A virtual environment install is on Installation.Connect your assistant
graphify install
graphify install --platform cursor
Map a repository
Open a repository in your assistant, then enter this in its chat:In Codex, select the Graphify skill with
/graphify .
$graphify and ask it to map the current repository. This is an assistant instruction, not a shell command.Code is parsed locally. If the repository includes documents or media, the skill can use your assistant’s model for semantic extraction. For an explicit code-only run, use the local CLI workflow.Inspect the output
graphify-out/
├── graph.html Interactive graph
├── GRAPH_REPORT.md Concepts, communities, and suggested questions
└── graph.json The graph used by CLI and MCP queries
graph.html in your browser. Click a node to inspect its connections, or start with the report for a tour of the architecture.Ask a question
From a terminal at the repository root:Use names from your graph to investigate further:The names above are placeholders. A path only exists if those nodes and connecting edges exist in your project.
graphify query "how does authentication reach the database?"
graphify explain "YourService"
graphify path "YourService" "YourRepository"
Take the full tutorial
Build a small example and follow a real relationship.
Give your agent MCP tools
Expose the graph as structured tools in your editor.
Assistant
Responses are generated using AI and may contain mistakes.
