Graphify

Graphify turns each git repo in a folder into a queryable knowledge graph and points the agent at it, so sessions answer “what is X” and “how does A reach B” from the graph instead of reading files. The graph is built by a deterministic tree-sitter pass — no LLM, no network, no tokens — and a per-repo visualizer page draws it with community clustering and confidence-coded edges.

The Graphify visualizer: the repo's graph with community clusters, a search box, and per-repo switches and counts

Nothing runs until it is switched on: the folder carries a Graphify switch and each repo inside it carries its own, both default off. Flip them on the page, or let a session do it — graphify_build switches graphify on for its folder and repo, then builds. While a switch is off, graphify_path and graphify_explain refuse and tell the agent to call graphify_build. Every provider’s base prompt explains how to use the tools; when switched on, the plugin also sets a session system prompt describing the repo’s graph so the agent reaches for the tools first — graphify_path even returns a diagram of the hop chain that the chat renders inline.

Tool What it does
graphify_build Builds or refreshes the repo’s graph; incremental by default (per-file hash cache)
graphify_path Shortest path between two concepts, hop by hop with relation and confidence, plus a diagram
graphify_explain One concept: where it is defined, every direct neighbour, its community, and degree rank

Edges carry a confidence — EXTRACTED (stated in source), INFERRED (deduced), or AMBIGUOUS — and the visualizer keys its dashed edge styles to them in a legend. The page opens from a project, a session, or a folder row on the Folders page, and shows each repo’s node, edge, and community counts, its confidence split, and its highest-degree “god nodes”. The graph is code-only: it parses common source extensions (Python, TypeScript, JavaScript, Go, Rust, Java, C/C++, Ruby, Swift, Kotlin, C#, Scala, PHP) and does not read docs, PDFs, or images.

Installing the graphify engine, settings, and permissions

The graph builder is the graphifyy Python package. When it is missing, a tool tells the agent to ask you for approval and then install python3, pip, and graphifyy itself through the App Manager’s app_install tool. Every install banner on the page also offers an Install from App Manager button with the request prefilled, alongside a manual command — graphify never installs anything behind your back. A legacy self-install into a private venv stays behind the off-by-default auto_install setting.

Settings: python_bin (python3 or python, default python3), auto_install (default off), prompt_mode (when_graph_exists, always, or off — whether to set the session system prompt), path_image (default on — return found paths as chat-rendered diagrams), and build_timeout_secs (30–600, default 600).

Hooks: mcp.tool.invoke, http.request.before, http.request.authed, session.message.before (observed only, to sync the system prompt). Permissions: provide_mcp_tools, process_exec, project_files_read, data_store, session_read, session_prompt_write, user_authority, contribute_sidebar.


Assembled with many small pecks.

This site uses Just the Docs, a documentation theme for Jekyll.