跳到主要内容
Supermarket
返回能力市场
Agent Pack
data
Apache-2.0

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, every edge explained, no vector store.

Graphify-LabsGraphify-Labs
59/ 100

公开评测 · 综合采用结论

存在需要人工复核的风险或证据不足

查看评测依据 查找我项目的报告基于公开项目证据,非安全认证或安装推荐
149.2kstars
14.3kforks
最近更新 16小时前
评测生成时间(北京时间)
本报告引擎
v3.8.0
当前引擎
v3.17.3

本报告与当前引擎使用不同规则;原分数不会自动更新,不同版本的分数不宜直接对比。

重新评测此项目

进入后确认来源与额度,提交才会创建任务。

代码版本未记录或记录无效,无法核对本报告的 commit 与送评文本;不会用当前项目代码回填历史记录。

Evaluation report

综合采用结论

59
D
满分 100 · 静态采用参考
谨慎采用高风险
决策摘要

存在需要人工复核的风险或证据不足

84%
高置信度
95
文档
56
安全
79
质量
100
活跃
70
采用
  • 基础评测完成+25/25确定性评分与静态安全扫描已完成
  • README 有效证据+25/2552,132 个去重后的有效字符
  • 独立证据来源+4/201 类非重复证据,重复文件不叠加
  • 仓库元数据+10/10已取得仓库状态与采用数据
  • 活跃记录+5/5已取得最近提交时间
  • AI 复核+15/15已完成结构化 AI 证据复核

本报告评了什么

综合分用于静态采用筛选,不是任务成功率,也不代表使用 Skill 后的能力提升。

静态检查范围
记录 1 个文件 · 61,827 字符
只检查采集到的受限文本与已知风险模式;未读取的脚本、依赖和运行环境不在结论内。
AI 内容复核
已使用
复核送评文本的说明和设计,不是安装测试或实际任务执行。记录缺失时不推断已使用或未使用。
真实任务效果
本报告未提供实测证据
没有使用/不使用 Skill 的任务对照、重复运行或耗时与 token 成本结果。采用前仍需在隔离环境验证自己的任务。

脚本引用覆盖

脚本引用覆盖记录不可得;不推断没有引用或已经检查。

How it works · 流程图

Graphify 工作流程

README 描述了从安装到生成图谱的连续步骤,包括命令和输出。

AI 提取 · 证据约束

左右滑动查看完整图示

Graphify 工作流程README 描述了从安装到生成图谱的连续步骤,包括命令和输出。然后然后触发生成安装CLI用户操作注册技能用户操作运行/graphify用户操作提取代码系统处理生成输出系统结果
图示依据
  • • 安装命令: uv tool install graphifyy
  • • 注册: graphify install
  • • 运行: /graphify .
五维表现
将代码库映射为可查询知识图谱,解决真实检索痛点,本地AST解析保证确定性。安装与多平台接入清晰,但文档未提供许可证信息,且部分高级功能依赖外部API。
质量证据
  • 安装命令: uv tool install graphifyy
  • 平台支持: 20+ assistants 列表
  • 输出文件: graph.html, GRAPH_REPORT.md, graph.json
  • 排障: 'graphify: command not found' 解决方案
  • 限制: 高级功能需额外extras
采用建议
优势
  • 问题与用途描述
  • 有效 README
  • 安装或接入步骤
  • 可执行示例
  • 本地AST解析,无LLM,确定性高
关注点
  • 发现高风险的一键下载执行或安装命令
  • 缺少许可证信息
  • 高级功能依赖外部API,可能涉及数据外发
  • 部分平台支持需额外配置
  • 文档未明确错误处理细节
适合

需要快速理解大型代码库的开发者、希望本地化、无云端依赖的团队、多语言项目知识管理、集成多种AI助手的用户

不建议直接用于

对数据隐私要求极高且不允许任何外部API调用的场景、需要完整许可证合规性的企业环境

也有自己的公开项目?先免登录查已有报告;没有报告时,可保留地址继续登录评测。

查找我项目的报告 →
文档证据
95/100
问题与用途描述10 分
有效 README12 分
安装或接入步骤14 分
可执行示例16 分
输入、参数或工具说明11 分
输出或结果说明9 分
限制、权限或边界12 分
错误处理或排障8 分
许可证信息5 分
结构化章节3 分
安全证据
高风险
发现高风险的一键下载执行或安装命令
unsafe-install-commandREADME.md:136high confidence
| uv *(recommended)* | any | `uv --version` | `curl -LsSf https://astral.sh/uv/install.sh \| sh` |

修复:固定版本与校验和,先下载审查再执行,避免管道直接交给 Shell。

发现高风险的一键下载执行或安装命令
unsafe-install-commandREADME.md:153high confidence
curl -LsSf https://astral.sh/uv/install.sh | sh

修复:固定版本与校验和,先下载审查再执行,避免管道直接交给 Shell。

优先改进清单
  1. 01固定版本与校验和,先下载审查再执行,避免管道直接交给 Shell。
  2. 02补充许可证信息
方法、证据与局限展开
数据来源

GitHub Repository API

扫描范围

1 个文件 · 61,827 字符

评测引擎

v3.8.0 · AI 内容复核:已使用(deepseek-chat)

局限
  • 静态评测不会安装或执行项目代码
  • 安全扫描基于高信号文件与已知模式,不能替代人工审计
  • 流行度只反映采用程度,不代表安全或工程质量

30 天热度趋势

README

Graphify

Graphify-Labs%2Fgraphify | Trendshift

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 | עברית

PyPI CI License: Apache-2.0 Downloads Docs Graphify Cloud Discord YouTube LinkedIn YC S26

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. Start a free 14-day trial →

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) or INFERRED (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 a free 14-day trial at app.graphify.com.

graphify's interactive graph.html showing the FastAPI codebase as a force-directed knowledge graph with a legend of detected communities

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

graphify path query: a terminal asks for the shortest path between FastAPI and ModelField, and the answer lights up hop by hop across the knowledge graph

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 "<question>" 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:

CapabilityWhat you get
God nodesThe most-connected concepts, so you see what everything flows through
CommunitiesThe graph split into subsystems (Leiden), with LLM-free labels
Cross-file linkscalls / imports / inherits / mixes_in resolved across ~40 languages via tree-sitter AST
Query, path, explainAsk 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 codeDocs, PDFs, images, and video/audio all map into the same graph
Local-firstCode 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 a free 14-day trial →


Benchmarks: 0.497 recall@10, 0 LLM credits

BenchmarkMetricgraphifyField
LOCOMO (n=300)recall@100.497mem0 0.048, supermemory 0.149
LOCOMO (n=300)QA accuracy45.3%supermemory 49.7%, mem0 27.3%
LongMemEval-S (n=50)QA accuracy76%tied with dense RAG
ERPNext cross-tool (n=6)key-fact coverage82.0%grep/read baseline 70.8%
Graph buildLLM credits0per-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:


Prerequisites

RequirementMinimumCheckInstall
Python3.10+python --versionpython.org
uv (recommended)anyuv --versioncurl -LsSf https://astral.sh/uv/install.sh | sh
pipx (alternative)anypipx --versionpip install pipx

macOS quick install (Homebrew):

brew install python@3.12 uv

Windows quick install:

winget install astral-sh.uv

Ubuntu/Debian:

sudo apt install python3.12 python3-pip pipx
# or install uv:
curl -LsSf https://astral.sh/uv/install.sh | sh

Install

[!IMPORTANT] Official package: The PyPI package is graphifyy (double-y). Other graphify* packages on PyPI are not affiliated. The CLI command is still graphify.

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] Hitting command not found, a pip-on-Mac/Windows issue, PowerShell quoting, uvx usage, git-hook PATH quirks, or strict mode? See Installation and Troubleshooting.

Pick your platform (20+ assistants, click to expand)
PlatformInstall command
Claude Code (Linux/Mac)graphify install
Claude Code (Windows)graphify install (auto-detected) or graphify install --platform windows
CodeBuddygraphify install --platform codebuddy
Codexgraphify install --platform codex
OpenCodegraphify install --platform opencode
Kilo Codegraphify install --platform kilo
GitHub Copilot CLIgraphify install --platform copilot
VS Code Copilot Chatgraphify vscode install
Aidergraphify install --platform aider
OpenClawgraphify install --platform claw
Factory Droidgraphify install --platform droid
Traegraphify install --platform trae
Trae CNgraphify install --platform trae-cn
Gemini CLIgraphify install --platform gemini
Hermesgraphify install --platform hermes
Kimi Codegraphify install --platform kimi
Ampgraphify amp install
Agent Skills (cross-framework)graphify install --platform agents (alias --platform skills)
Kiro IDE/CLIgraphify kiro install
Pi coding agentgraphify install --platform pi, plus graphify pi guard install for the native guard
Cursorgraphify cursor install
Devin CLIgraphify devin install
Google Antigravitygraphify 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.

Pi has no PreToolUse hook, so graphify pi guard install registers a native Pi extension (via Pi's own pi install <package directory>) 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 indexed-read denial come from that same policy, so Pi matches Claude Code's hook behavior; guidance arrives as a <system-reminder source="graphify"> 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 <old path>.

Codex uses $graphify instead of /graphify.

Optional extras (install only what you need)
ExtraWhat it addsInstall
pdfPDF extractionuv tool install "graphifyy[pdf]"
office.docx and .xlsx supportuv tool install "graphifyy[office]"
googleGoogle Sheets renderinguv tool install "graphifyy[google]"
videoVideo/audio transcription (faster-whisper + yt-dlp)uv tool install "graphifyy[video]"
mcpMCP stdio serveruv tool install "graphifyy[mcp]"
watchAuto-rebuild on file changes (graphify watch)uv tool install "graphifyy[watch]"
neo4jNeo4j push supportuv tool install "graphifyy[neo4j]"
falkordbFalkorDB push supportuv tool install "graphifyy[falkordb]"
svgSVG graph exportuv tool install "graphifyy[svg]"
leidenLeiden community detection (graspologic on Python < 3.13; native backend on 3.13+)uv tool install "graphifyy[leiden]"
ollamaOllama local inferenceuv tool install "graphifyy[ollama]"
openaiOpenAI / OpenAI-compatible APIsuv tool install "graphifyy[openai]"
geminiGoogle Gemini APIuv tool install "graphifyy[gemini]"
anthropicAnthropic Claude API (--backend claude, uses ANTHROPIC_API_KEY)uv tool install "graphifyy[anthropic]"
bedrockAWS Bedrock (uses IAM, no API key)uv tool install "graphifyy[bedrock]"
azureAzure OpenAI Service (--backend azure, uses AZURE_OPENAI_API_KEY + AZURE_OPENAI_ENDPOINT)uv tool install "graphifyy[openai]"
sqlSQL schema extractionuv tool install "graphifyy[sql]"
postgresLive PostgreSQL introspection (--postgres DSN)uv tool install "graphifyy[postgres]"
dmBYOND DreamMaker .dm/.dme AST extraction (may need a C compiler + python3-dev if no wheel matches your platform)uv tool install "graphifyy[dm]"
terraformTerraform / HCL .tf/.tfvars/.hcl AST extractionuv tool install "graphifyy[terraform]"
pascalPascal / 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]"
ocamlOCaml .ml/.mli AST extractionuv tool install "graphifyy[ocaml]"
commonlispCommon Lisp .lisp/.cl/.lsp/.asd AST extractionuv tool install "graphifyy[commonlisp]"
robotRobot Framework .robot/.resource extraction (suites, test cases, keywords, keyword-call and resource/library import edges)uv tool install "graphifyy[robot]"
chineseChinese query segmentation (jieba)uv tool install "graphifyy[chinese]"
allEverything aboveuv tool install "graphifyy[all]"

Make your assistant always use the graph

Run this once in your project after building a graph:

Run graphify <platform> install once in your project, for example graphify claude install or graphify codex install (or graphify install --platform <name>).

This writes a small config file that tells your assistant to consult the knowledge graph for codebase questions, preferring scoped queries like graphify query "<question>" 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) 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:

SetupGuidance to useQuery access
Local CLI and installed assistant skillThe platform instructions written by graphify installRun graphify query, graphify path, and graphify explain against the local graph (graphify-out/ by default).
Connected Graphify MCP serverThe connection's instructions and the tools listed by that serverCall the listed MCP tools against the graph served by that connection. Tool names and descriptions come from the server.

Both encourage scoped graph queries before broad source searches. Choose the instructions that match the tools your assistant can actually access; neither block establishes a universal precedence rule for your assistant's instruction files. If you use both integrations, identify which graph each queries and choose a primary query path instead of copying two unconditional instruction blocks into AGENTS.md.

graphify install installs the local assistant integration; it does not establish an MCP connection. An MCP client does not need to run local CLI queries to use its connected server. A locally hosted server still needs its own Graphify installation and graph, while a hosted connection may serve a graph that is not present in the client's working directory. If the expected tools are missing, check the relevant CLI installation or MCP connection rather than treating the other setup's instructions as interchangeable.


What's in the report

GRAPH_REPORT.md summarizes the god nodes, communities, and key paths for broad architecture review. How the graph is built and what it contains: How graphify works.


What files it handles: ~40 languages

graphify parses ~40 programming languages locally with tree-sitter AST, and maps docs, PDFs, images, and audio/video through an optional semantic pass. Full list: Supported inputs.


Common commands

/graphify .                        # build graph for current folder
/graphify ./docs --update          # re-extract only changed files
/graphify . --cluster-only         # rerun clustering without re-extracting
/graphify . --cluster-only --resolution 1.5      # more granular communities
/graphify . --cluster-only --exclude-hubs 99     # suppress utility super-hubs from god-node rankings
/graphify . --no-viz               # skip the HTML, just the report + JSON
/graphify . --wiki                 # build a markdown wiki from the graph
graphify export callflow-html      # Mermaid architecture/call-flow HTML (auto-regenerates on every git commit if hook is installed)

/graphify query "what connects auth to the database?"
/graphify path "UserService" "DatabasePool"
/graphify explain "RateLimiter"

/graphify add https://arxiv.org/abs/1706.03762   # fetch a paper and add it
/graphify add <youtube-url>                       # transcribe and add a video

graphify hook install              # auto-rebuild on commit + branch checkout (run `graphify update .` after `git pull`: see "Recommended workflow" below)
graphify merge-graphs a.json b.json              # combine two graphs

graphify prs                       # PR dashboard: CI state, review status, worktree mapping
graphify prs 42                    # deep dive on PR #42 with graph impact
graphify prs --triage              # AI ranks your review queue (uses whatever backend is configured)
graphify prs --conflicts           # PRs sharing graph communities: merge-order risk

See the full command reference below.


Labeling and rendering limits

  • --batch-size: 100 communities per labeling call by default, sized for a ~16k-token context (~150 tokens/community). Use --batch-size 40 for an 8k window. Context overflow is not split-retried; failed batches keep hub-derived names.
  • --missing-only: label --missing-only keeps existing labels and names only unnamed / Community N entries. Use label (full relabel) to refresh names after the community set changes.
  • .graphify_labels.json.sig: records the community membership signature; labels survive a re-cluster only while it matches.
  • export html: 5,000-node default; above it graphify renders an aggregated community view. Use --node-limit N. GRAPHIFY_VIZ_NODE_LIMIT / .graphifyrc viz_node_limit=N apply to cluster-only, update, watch, and hooks, not export html.
  • Leiden fallback: without the leiden extra, clustering silently uses networkx Louvain. Switching later reshuffles every community, so plan a full relabel.

Ignoring files

graphify honors .gitignore and supports --exclude patterns and a project .graphifyignore. Details: Configuration.

Project configuration

Create a .graphifyrc in the scan root for settings that belong to the project rather than to one run. One key=value per line; lines beginning with # are comments.

Ambiguous extensions. Some extensions mean different languages in different projects: .inc is PHP on pfSense, Pascal in a Delphi tree, SQL or assembly elsewhere; .h is C or C++; .m is Objective-C or MATLAB. graphify has to pick one global default, and when it picks wrong the file does not fail: it parses as the wrong language and yields a handful of incidental nodes, so the graph looks populated while the real symbols are missing. Declare what the extension means in your repo:

# .graphifyrc
# A language name:
language.inc=php
# Or an extension graphify already knows:
language.tpl=.ts
# Baked into the git hooks (see Team setup):
viz_node_limit=0

The declaration flows through classification, extractor selection, grammar and resolution, imports, graphify watch, and the AST cache (a file re-parsed under a different language never reuses the old entry), and the same .graphifyrc is read by extract, update, the hooks, the MCP server, and the /graphify skill. A typo is reported once on stderr and the scan continues with the defaults. How declarations interact with caching, incremental rebuilds, and import resolution: Configuration.


Team setup

Commit or share the graph so your whole team queries the same context, and review pull requests with graph context. See Share context with your team and Review pull requests.


Using the graph directly

Beyond your AI assistant, query graph.json straight from the CLI with graphify query, graphify path, and graphify explain. A name that matches several nodes is refused with the candidates listed rather than guessed. Scripts can read the outcome from the exit code: 0 an answer, 3 an ambiguous name, 4 no matching node. See Ask better graph questions and the query reference.


Environment variables

Backends, API keys, hook behavior, and tuning are controlled by environment variables. Full table: Configuration.

  • Claude API prompt caching: GRAPHIFY_CLAUDE_PROMPT_CACHE controls system-prompt caching for --backend claude. Unset or blank keeps caching enabled; 1, true, yes, or on explicitly enables it, and 0, false, no, or off disables it (case-insensitive, surrounding whitespace ignored). Invalid values raise an error before sending a request. For example, run GRAPHIFY_CLAUDE_PROMPT_CACHE=0 graphify extract . --backend claude when an Anthropic-compatible endpoint rejects cache_control. Disabling sends the original plain-text system prompt. The setting applies equally to official Anthropic and custom ANTHROPIC_BASE_URL / ANTHROPIC_MODEL endpoints, including deep mode; it does not affect Bedrock, Claude CLI, or Graphify's local extraction cache. Enabling requests caching but cannot guarantee cache hits: the endpoint/model must support it and the prompt must meet its minimum length. Unsupported caching errors are not silently retried without caching.
  • Claude CLI model: GRAPHIFY_CLAUDE_CLI_MODEL overrides the model for the claude-cli backend (default: Opus). haiku or sonnet are usually enough for community naming; the semantic extraction pass benefits from a larger model.

Privacy

  • Code files: processed locally via tree-sitter. Nothing leaves your machine. A code-only corpus requires no API key: graphify extract runs fully offline. On a mixed repo, add --code-only to index just the code and skip the docs/PDFs/images that would otherwise need an LLM.
  • Video / audio: transcribed locally with faster-whisper. Nothing leaves your machine.
  • Docs, PDFs, images: sent to your AI assistant for semantic extraction (via the /graphify skill, using whatever model your IDE session runs). Headless graphify extract requires GEMINI_API_KEY / GOOGLE_API_KEY (Gemini), MOONSHOT_API_KEY (Kimi), ANTHROPIC_API_KEY (Claude), OPENAI_API_KEY (OpenAI), DEEPSEEK_API_KEY (DeepSeek), a running Ollama instance (OLLAMA_BASE_URL), AWS credentials via the standard provider chain (Bedrock - no API key needed, uses IAM), or the claude CLI binary (Claude Code - no API key needed, uses your Claude subscription). The --dedup-llm flag uses the same key.
  • Data residency: graphify extract auto-detects which provider to use based on which API key is set (priority: Gemini → Kimi → Claude → OpenAI → DeepSeek → Azure → Bedrock → Ollama). When it auto-detects, it prints the exact environment variable that chose the provider, so a run is never a surprise. To choose explicitly, pass --backend, or set GRAPHIFY_BACKEND=<name>; set GRAPHIFY_BACKEND=none to disable all LLM backends (semantic extraction and the claude -p labeling fallback) and keep a code-only graph. For code with data-residency requirements, use GRAPHIFY_BACKEND=ollama / --backend ollama (fully local). Kimi (MOONSHOT_API_KEY) routes to Moonshot AI servers in China.
  • No telemetry, no usage tracking, no analytics.
  • Query logging: every graphify query, graphify path, graphify explain, and MCP query_graph call is logged to ~/.cache/graphify-queries.log in JSON Lines format (timestamp, question, corpus, nodes returned, duration). Full subgraph responses are not stored by default. Set GRAPHIFY_QUERY_LOG_DISABLE=1 to opt out, or GRAPHIFY_QUERY_LOG=/dev/null to silence without disabling the code path.

Troubleshooting

Common install and extraction issues and their fixes: Troubleshooting.


Full command reference

Every command and flag, with examples: CLI reference.


Learn more


Graphify Cloud

Graphify Cloud is the always-on layer built on top of graphify. Instead of a graph you rebuild on demand per folder, it keeps one live graph across your entire software development lifecycle:

  • 80% fewer tokens: always-on memory means your agents stop re-reading and re-explaining the codebase every session.
  • Monorepo and cross-repo: one connected graph across every service and repository, not a graph per folder.
  • Formal verification: check architectural and dependency invariants against the live graph.
  • Code review with a bird's-eye view of your SDLC: see how a change ripples across the whole system before you merge.
  • SDLC connectors: pull in Sentry, Jira, and more, so incidents, tickets, and code live in one graph.
  • Always-on: updates continuously in the background across code, docs, and meetings.

Start a free 14-day trial at app.graphify.com →


Contributing

Contributions are welcome. See CONTRIBUTING.md for the development setup, the test and CI-parity commands, the git workflow, and what makes a strong contribution (worked examples and extraction bug reports are the most useful). Architecture and how to add a language: ARCHITECTURE.md.

New here? Say hi on Discord or in GitHub Discussions.


Contributors

graphify contributors

Made with contrib.rocks.


Translations

The README is available in 32 languages. Use the language switcher at the top of this file to read it in yours, or browse docs/translations/. To improve a translation or add a new one, open a pull request against the matching file there.


Building on graphify

Building something in the graphify ecosystem? That is encouraged. If your project uses "graphify" in its name (for example graphify-dashboard or graphify-action), please add a short note to your README clarifying that it is community-built and not affiliated with or endorsed by Graphify Labs. "graphify" and the graphify logo are marks of Graphify Labs; please do not use them in a way that implies official status.


Community and links

Website Discord X YouTube Sponsor The Memory Layer