Graphify Turns Your Codebase Into a Knowledge Graph to Give AI Agents Real Context
The open-source tool converts repositories, docs, and mixed files into queryable knowledge graphs, aiming to fix the multi-file blind spots of AI coding assistants.
The problem it targets
As AI coding assistants become central to development, giving large language models accurate cross-file awareness has become a real bottleneck. As InfoQ's Olimpiu Pop reported, traditional coding assistants often struggle with multi-file reasoning and deep dependencies because they treat a repository as an isolated pool of text, running into context-window and memory limits. Graphify, an open-source utility, tries to bridge that gap by turning code and docs into a structured graph the model can navigate instead of brute-force reading files.
How Graphify works
According to InfoQ, Graphify runs a multi-stage pipeline: it scans target directories, extracts structural AST elements using tree-sitter alongside semantic cues from documentation, and builds a unified graph clustered through community-detection algorithms. Repositories and mixed folders become searchable nodes and edges. The output can be queried directly or wired into AI coding assistants through Model Context Protocol (MCP) servers, which the report says achieves substantial token reductions compared with naive file-reading approaches. It handles multiple input types, including code, Markdown or PDF documentation, and even images.
Licensing, availability and traction
The project first kicked off in April 2026 under dual MIT and Apache-2.0 licenses and, per InfoQ, crossed thousands of GitHub stars within its first ten days. It follows a fast release cadence of multiple updates per month. Graphify is available on macOS, Windows and Ubuntu/Linux and can be installed via uv.
What's new in recent releases
InfoQ notes recent iterations have focused on deeper language-parser intelligence and fewer false positives. Highlights include Terraform block attribute preservation (keeping infrastructure config queryable alongside source), and cross-file method resolution upgrades such as split impl-block support for generic types in Rust, external receiver tracking for Kotlin, and scope-qualified static call routing for C++. Other additions include smart Markdown code-span tracking that maps inline docs to code symbols, embedded script indexing inside PHP files, and cleaner dependency mapping for subpath package imports.
The benchmarks
Graphify's first-party benchmarks, as cited by InfoQ, report a LOCOMO recall@10 of 0.497, 45.3% QA accuracy, 76% on a 50-question LongMemEval-S subset, and an ERPNext key-fact coverage lift from 70.8% to 82.0% across six questions. As with any self-reported numbers, these are the project's own results rather than independent evaluation.
The honest caveats
InfoQ's writeup gives a nuanced picture of maturity. Feedback on communities like r/ClaudeAI and independent engineering blogs praises the concept as promising for large-scale repo orientation, onboarding and architectural reviews. But day-to-day integration is mixed: some developers love the context-mapping inside tools like Claude Code, while others note that for mid-sized repositories, brute-force navigation or plain grepping can still feel faster until the graph tooling matures. The community reads Graphify as a visionary step for agentic coding workflows that should sharpen as its parsing backend evolves.
Related on Skillo
See also: JetBrains unveils JetBrains Air agentic dev system, Open-source ChatGPT alternatives you can run locally.
Sources
Published date reflects the original event date (2026-09-24). This article is original Skillo editorial written from the sources above; facts were verified in September 2026.
Written by
Skillo Staff
0 Comments
Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.