Getting started

Install

npm install -g @nodesify/graphify

Requires no Rust toolchain — ships prebuilt native binaries via napi-rs. Node.js >= 20.

Build your first graph

Drop into any project folder and run:

nodesify-graphify run .

This runs the full pipeline — detect → extract → build → cluster → analyze → report — and creates a .graphify/ directory containing:

• db.sqlite — the graph database
• graph.json — full graph export
• graph_report.md — report with hub nodes, communities, surprising connections

Combine building with a wiki export or embeddings in one step:

nodesify-graphify run . --wiki    # ...also export a markdown wiki to .graphify/wiki
nodesify-graphify run . --embed   # ...also compute local embeddings (similar_to edges + semantic query recall)

Keep it fresh

nodesify-graphify update <path>                    # Incremental rebuild (only changed files; regenerates an existing wiki)
nodesify-graphify watch <path> [--debounce 3000]   # Watch for file changes, auto-rebuild

update only re-extracts files that changed since the last run, so large repos rebuild in seconds.

Query it

nodesify-graphify explain <node>                  # Explain a node and its connections
nodesify-graphify query "where does auth live"    # BFS traversal with a token budget
nodesify-graphify path <A> <B>                    # Shortest path between two concepts
nodesify-graphify affected <node>                 # Blast radius - what breaks if you change this node
nodesify-graphify map                             # PageRank-ranked repo map with top symbols

See the CLI reference for every command and flag.

Use it from AI agents

nodesify-graphify mcp          # Run MCP stdio server - query the graph from any AI agent
nodesify-graphify install      # Install skill files for AI coding assistants

mcp exposes the graph over the Model Context Protocol, so any MCP-capable agent (Claude Code, Codex, Cursor, …) can query it. install writes skill files for your assistant of choice:

Supported platforms: claude, codex, gemini, cursor, copilot, aider, opencode, kiro, trae.

Git hooks can keep the graph fresh automatically:

nodesify-graphify hook install|uninstall|status

Excluding files

Place a .graphifyignore file in your project root (gitignore syntax) to exclude files from the graph.

Where the token savings come from

Every run and update prints an honest cost measurement: corpus tokens (the real file sizes from the manifest) versus the tokens a graph query actually returns, sampled over five representative questions. On this repository: ~221,000 corpus tokens vs ~3,000 per query — 73× fewer tokens per query. On tiny corpora it will honestly report <1×; there the graph's value is structure, not compression, and the output says so.