Graphify-Labs/graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing
About Graphify-Labs/graphify
Graphify-Labs/graphify is an open-source project on GitHub, mainly written in Python. Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. It currently holds 138,244 stars and 13,176 forks with 1,646 open issues, and was last pushed on 2026-10-27 (repository created 2026-04-03).
Project Overview
Git Homed tracks it on the AI Agent Skills Trending board and on the AI AI Agent Skills Trending list, currently at rank #20 with 615 new stars today.
GitHub Repository Details
README
Read this in other languages
English | 简体中文 | 日本語 | 한국어 | Deutsch | Français | Español | हिन्दी | Português | Русский | العربية | فارسی | Italiano | Polski | Nederlands | Türkçe | Українська | Tiếng Việt | Bahasa Indonesia | Svenska | Ελληνικά | Română | Čeština | Suomi | Dansk | Norsk | Magyar | ภาษาไทย | Oʻzbekcha | 繁體中文 | Filipino | עברית
Start free, no card required →
Cut agent token spend by 80%. Graphify Cloud is always-on memory that governs your agents, keeps code quality high, and proves correctness with formal verification.
Type /graphify in your AI coding assistant and it maps your entire project (code, docs, PDFs, images, videos) into a knowledge graph you can query instead of grepping through files.
- Code maps for free, fully local. Code is parsed with tree-sitter AST: deterministic, no LLM, nothing leaves your machine. (Docs, PDFs, images and video use your assistant's model, or a configured API key, for a semantic pass.)
- Every edge is explained. Each connection is tagged
EXTRACTED(explicit in the source) orINFERRED(resolved by graphify), so you can tell what was read directly from what was inferred. - Not a vector index. No embeddings, no vector store: a real graph you traverse. Ask a question, trace the path between two things, or explain one concept.
[!NOTE]
Want this always-on? Graphify Cloud keeps the graph live across your entire SDLC: monorepo and cross-repo support, formal verification, and code review with a bird's-eye view of your SDLC, plus connectors for Sentry, Jira, and more so incidents and tickets sit in the same graph as your code. Start free, no card required.
The FastAPI codebase mapped by graphify. Every node is a concept, colors are detected communities, and the whole thing is clickable in graph.html.
Get started (30 seconds). Needs Python 3.10+ and uv (or pipx):
uv tool install graphifyy # install the CLI (or: pipx install graphifyy)
graphify install # detects your assistant and registers the skill
Then, in your AI assistant:
/graphify .
That's it. You get three files:
graphify-out/
├── graph.html open in any browser: click nodes, filter, search
├── GRAPH_REPORT.md the highlights: key concepts, surprising connections, suggested questions
└── graph.json the full graph: query it anytime without re-reading your files
The persisted graph includes graph.schema_version so integrations can detect
incompatible format changes, plus graph.graphify_version identifying the
Graphify release that produced it.
One install, any assistant, any OS. Claude Code, Cursor, Codex, Gemini CLI, GitHub Copilot, and 20+ more, on macOS, Linux, and Windows: pick your platform.
---
See it in action
Once the graph is built you query it instead of reading files. Real output, graphify run on the FastAPI codebase shown above:
$ graphify explain "APIRouter"
Node: APIRouter
Source: routing.py L2210
Community: 2
Degree: 47
Connections (47):
--> RequestValidationError [uses] [INFERRED]
--> Dependant [uses] [INFERRED]
--> .get() [method] [EXTRACTED]
<-- __init__.py [imports] [EXTRACTED]
...
$ graphify path "FastAPI" "ModelField"
Shortest path (3 hops):
FastAPI --uses--> DefaultPlaceholder <--references-- get_request_handler() --references--> ModelField
Every edge carries a confidence tag (EXTRACTED = explicit in the source, INFERRED = derived by resolution), so you can tell what was read directly from what was inferred. graphify query "" returns a scoped subgraph for a plain-language question, and graphify path A B traces how any two things connect, ending with the path's overall confidence: that of its weakest hop.
---
What it does
What you get out of the box:
| Capability | What you get |
|---|---|
| God nodes | The most-connected concepts, so you see what everything flows through |
| Communities | The graph split into subsystems (Leiden), with LLM-free labels |
| Cross-file links | calls / imports / inherits / mixes_in resolved across ~40 languages via tree-sitter AST |
| Query, path, explain | Ask a question, trace the path between two things, or explain one concept, all against graph.json |
| Rationale + doc refs | # NOTE: / # WHY: comments and ADR/RFC citations become first-class nodes linked to the code |
| Beyond code | Docs, PDFs, images, and video/audio all map into the same graph |
| Local-first | Code is parsed locally with tree-sitter (no LLM, nothing leaves your machine); only the semantic pass over docs/media calls a backend, and only if you configure one |
[!TIP]
Running this across many repos or a monorepo? Graphify Cloud does it continuously and cuts agent token spend by 80%, with cross-repo links, SDLC-wide code review, formal verification, and Sentry/Jira connectors. Start free, no card required →
---
Benchmarks: 0.497 recall@10, 0 LLM credits
| Benchmark | Metric | graphify | Field | |---|---|---|---| | LOCOMO (n=300) | recall@10 | 0.497 | mem0 0.048, supermemory 0.149 | | LOCOMO (n=300) | QA accuracy | 45.3% | supermemory 49.7%, mem0 27.3% | | LongMemEval-S (n=50) | QA accuracy | 76% | tied with dense RAG | | ERPNext cross-tool (n=6) | key-fact coverage | 82.0% | grep/read baseline 70.8% | | Graph build | LLM credits | 0 | per-token for most systems |
Every system ran on the same harness with the same model and budgets, scored by a judge blind-validated against a second judge (90.6% agreement, Cohen's kappa 0.81). Full per-system tables, the code-intelligence result, and reproduction commands: BENCHMARKS.md.
---
Documentation
Full guides and reference live at docs.graphify.com:
- Quickstart: build your first graph
- CLI reference: every command and flag
- Ask better graph questions: querying patterns
- Configuration: environment variables and tuning
- Supported inputs: languages and file types
- Team workflows and PR review
- Troubleshooting and How it works
Prerequisites
| Requirement | Minimum | Check | Install |
|---|---|---|---|
| Python | 3.10+ | python --version | python.org |
| uv (recommended) | any | uv --version | curl -LsSf https://astral.sh/uv/install.sh \| sh |
| pipx (alternative) | any | pipx --version | pip install pipx |
macOS quick install (Homebrew):
brew install python@3.12 uv
Windows quick install:
winget install astral-sh.uv
Ubuntu/Debian:
# uv manages its own Python, so this is the only step you need:
curl -LsSf https://astral.sh/uv/install.sh | sh
or use the system Python with pipx:
sudo apt install python3 python3-pip pipx
---
Install
[!IMPORTANT]
Official package: The PyPI package isgraphifyy(double-y). Othergraphify*packages on PyPI are not affiliated. The CLI command is stillgraphify.
The official source repository is Graphify-Labs/graphify.
The two-command quickstart is at the top of this README. This section covers the install methods, project-scoped installs, and every supported platform.
Install methods (pick one):
uv tool install graphifyy # recommended, isolated env (if 'graphify' isn't found after, run: uv tool update-shell)
pipx install graphifyy # alternative
pip install graphifyy # may need PATH setup, see Troubleshooting below
Then run graphify install once. It detects which assistant you run and registers the skill, so there is no per-assistant setup. Open your AI assistant and type /graphify .
To install the assistant skill into the current repository instead of your user
profile, add --project:
graphify install --project
graphify install --project --platform codex
Project-scoped installs write under the current directory, for example
.claude/skills/graphify/SKILL.md or .agents/skills/graphify/SKILL.md (plus a
references/ sidecar the skill loads on demand), and
print a git add hint for files that can be committed.
Per-platform commands that support project-scoped installs accept the same flag,
for example graphify claude install --project or graphify codex install --project.
[!TIP]
Hittingcommand not found, apip-on-Mac/Windows issue, PowerShell quoting,uvxusage, git-hook PATH quirks, or strict mode? See Installation and Troubleshooting.
Pick your platform (20+ assistants, click to expand)
| Platform | Install command |
|----------|----------------|
| Claude Code (Linux/Mac) | graphify install |
| Claude Code (Windows) | graphify install (auto-detected) or graphify install --platform windows |
| CodeBuddy | graphify install --platform codebuddy |
| Codex | graphify install --platform codex |
| OpenCode | graphify install --platform opencode |
| Kilo Code | graphify install --platform kilo |
| GitHub Copilot CLI | graphify install --platform copilot |
| VS Code Copilot Chat | graphify vscode install |
| Aider | graphify install --platform aider |
| OpenClaw | graphify install --platform claw |
| Factory Droid | graphify install --platform droid |
| Trae | graphify install --platform trae |
| Trae CN | graphify install --platform trae-cn |
| Gemini CLI | graphify install --platform gemini |
| Hermes | graphify install --platform hermes |
| Kimi Code | graphify install --platform kimi |
| Amp | graphify amp install |
| Agent Skills (cross-framework) | graphify install --platform agents (alias --platform skills) |
| Kiro IDE/CLI | graphify kiro install |
| Pi coding agent | graphify install --platform pi, plus graphify pi guard install for the native guard |
| Cursor | graphify cursor install |
| Devin CLI | graphify devin install |
| Google Antigravity | graphify antigravity install |
| Google Antigravity (Windows) | graphify antigravity install (auto-detected on Windows) |
Codex users also need multi_agent = true under [features] in ~/.codex/config.toml for parallel extraction. CodeBuddy uses the same Agent tool and PreToolUse hook mechanism as Claude Code. Factory Droid uses the Task tool for parallel subagent dispatch. OpenClaw and Aider use sequential extraction (parallel agent support is still early on those platforms). Trae uses the Agent tool for parallel subagent dispatch and does not support PreToolUse hooks, so AGENTS.md is the always-on mechanism.
--platform agents (alias --platform skills) targets the generic cross-framework Agent-Skills locations: the spec's user-global ~/.agents/skills/ (read by npx skills and spec-compliant frameworks) for a global install, and ./.agents/skills/ for a project (--project) install. The bare graphify install stays single-platform (Claude Code) by design: use the named agents platform when you want the skill discoverable by any framework that reads .agents/skills.
Claude Code's graphify install --project --strict makes Read and dedicated Grep share one denial per session unless a recent graph query has oriented the agent (default 30 minutes). A Grep over a directory needs no indexed-file match; a Grep pinned to a single file is denied only when the graph indexes that file, as with Read. External and graph-output Grep targets produce neither a deny nor a nudge, in soft mode as well as strict mode, matching Read's scope. A graph marked needs_update never triggers a Grep denial. Bash searches and Glob stay advisory. GRAPHIFY_HOOK_STRICT=1 enables the policy without reinstalling; GRAPHIFY_HOOK_STRICT=0 disables it even when installed with --strict. Existing strict installs need a reinstall to add the search hook's --strict flag, or the environment override. Soft nudges are capped per session (GRAPHIFY_HOOK_NUDGE_CAP, default 5). After a context compaction, a SessionStart hook (matcher compact) resets that budget, the subagents' budgets and the strict denial, since the compacted context no longer holds the earlier nudges.
Pi has no PreToolUse hook, so graphify pi guard install registers a native Pi extension (via Pi's own pi install ) that runs the installed graphify hook-guard before Pi's read, grep, find and search-style bash calls. Fresh/stale graph decisions and the GRAPHIFY_HOOK_STRICT=1 once-per-session denial shared by indexed Read and dedicated Grep come from that same policy, so Pi matches Claude Code's hook behavior; Bash and file listing remain advisory. Guidance arrives as a ` steering message. It needs Pi 0.58.4 or newer: earlier versions let a steering message skip the rest of a parallel tool-call batch. The package ships inside the Graphify installation, so install Graphify persistently (uv tool install graphifyy or pipx install graphifyy, not uvx), restart Pi after installing or upgrading, and remove it with graphify pi guard uninstall. Only local file targets are inspected; the hook needs graphify on an absolute PATH entry outside the project, is bounded to a two-second, 256 KiB-in/64 KiB-out call, and fails open. The same package also loads in Oh My Pi: omp plugin install "$(graphify pi guard path)". The registered path contains the Python version and venv, so re-run graphify pi guard install after changing either, and remove the old entry with pi remove `.
Codex uses$graphifyinstead of/graphify.
Optional extras (install only what you need)
| Extra | What it adds | Install |
|---|---|---|
| pdf | PDF extraction | uv tool install "graphifyy[pdf]" |
| office | .docx and .xlsx support | uv tool install "graphifyy[office]" |
| google | Google Sheets rendering | uv tool install "graphifyy[google]" |
| video | Video/audio transcription (faster-whisper + yt-dlp) | uv tool install "graphifyy[video]" |
| mcp | MCP stdio server | uv tool install "graphifyy[mcp]" |
| watch | Auto-rebuild on file changes (graphify watch) | uv tool install "graphifyy[watch]" |
| neo4j | Neo4j push support | uv tool install "graphifyy[neo4j]" |
| falkordb | FalkorDB push support | uv tool install "graphifyy[falkordb]" |
| svg | SVG graph export | uv tool install "graphifyy[svg]" |
| leiden | Leiden community detection (graspologic on Python < 3.13; native backend on 3.13+) | uv tool install "graphifyy[leiden]" |
| ollama | Ollama local inference | uv tool install "graphifyy[ollama]" |
| openai | OpenAI / OpenAI-compatible APIs | uv tool install "graphifyy[openai]" |
| gemini | Google Gemini API | uv tool install "graphifyy[gemini]" |
| anthropic | Anthropic Claude API (--backend claude, uses ANTHROPIC_API_KEY) | uv tool install "graphifyy[anthropic]" |
| bedrock | AWS Bedrock (uses IAM, no API key) | uv tool install "graphifyy[bedrock]" |
| azure | Azure OpenAI Service (--backend azure, uses AZURE_OPENAI_API_KEY + AZURE_OPENAI_ENDPOINT) | uv tool install "graphifyy[openai]" |
| sql | SQL schema extraction | uv tool install "graphifyy[sql]" |
| postgres | Live PostgreSQL introspection (--postgres DSN) | uv tool install "graphifyy[postgres]" |
| dm | BYOND DreamMaker .dm/.dme AST extraction (may need a C compiler + python3-dev if no wheel matches your platform) | uv tool install "graphifyy[dm]" |
| terraform | Terraform / HCL .tf/.tfvars/.hcl AST extraction | uv tool install "graphifyy[terraform]" |
| pascal | Pascal / Delphi .pas/.dpr/.dpk/.inc AST extraction (more accurate calls/inherits edges; falls back to a regex extractor when absent) | uv tool install "graphifyy[pascal]" |
| ocaml | OCaml .ml/.mli AST extraction | uv tool install "graphifyy[ocaml]" |
| commonlisp | Common Lisp .lisp/.cl/.lsp/.asd AST extraction | uv tool install "graphifyy[commonlisp]" |
| robot | Robot Framework .robot/.resource extraction (suites, test cases, keywords, keyword-call and resource/library import edges) | uv tool install "graphifyy[robot]" |
| chinese | Chinese query segmentation (jieba) | uv tool install "graphifyy[chinese]" |
| all | Everything above | uv tool install "graphifyy[all]" |
---
Make your assistant always use the graph
Run this once in your project after building a graph:
Run graphify install once in your project, for example graphify claude install or graphify codex install (or graphify install --platform ).
This writes a small config file that tells your assistant to consult the knowledge graph for codebase questions, preferring scoped queries like graphify query "" over reading the full report or grepping raw files.
- Hook platforms (Claude Code, Gemini CLI): a hook fires automatically before search-style tool calls (and, on Claude Code, before reading source files one by one via the Read/Glob tools, or via
cat,head,tail,sed -nand similar readers in Bash) and nudges your assistant toward the graph path. - Instruction-file platforms (Codex, OpenCode, Cursor, etc.): persistent instruction files (
AGENTS.md,.cursor/rules/, etc.) provide the same query-first guidance.
GRAPH_REPORT.md is still available for broad architecture review.
Exactly which files each platform writes (CodeBuddy's CODEBUDDY.md + PreToolUse hooks, Codex's AGENTS.md, Kilo's native .kilo plugin, Cursor's alwaysApply rule, and so on) is covered in Always-on setup.
To remove graphify from all platforms at once: graphify uninstall (add --purge to also delete graphify-out/). Or use the per-platform command (e.g. graphify claude uninstall).
CLI skills or MCP instructions?
The instructions installed by graphify install and those supplied with a Graphify MCP connection describe different ways to query a graph:
| Setup | Guidance to use | Query access |
|---|---|---|
| Local CLI and installed assistant skill | The platform instructions written by graphify install | Run graphify query, graphify path, and graphify explain against the local graph (graphify-out/ by default).
