Source: github.com/graphicle-ai/graphicle
Graphicle runs locally as one install with one SQLite file, and its setup command connects Claude Code, Codex, Cursor, VS Code and Claude Desktop. Any other MCP client can be added with a short JSON entry. The README says no API key or account is needed for the code graph, sync, context retrieval or session capture.
The code-graph engine is a Rust port of Graphify and is kept in step with Graphify's releases. A model is needed only for written answers from graphicle ask and for proposing memories. Memories that agents propose wait for approval in a built-in app, and a memory is marked stale when the code it describes changes.
The README reports one exploratory run on a Kubernetes repository of 31k files, where a code-only extract took 3 min 18 s against 26 min 38 s for Graphify 0.9.88, with both producing the same graph. Native Windows support is not yet available, and the WSL2 path is untested.
Why it matters if you build agents
Developers building coding agents can give them cited code and project memory from a single local install instead of running a graph tool and a memory server separately. Because the code-graph engine is claimed to match Graphify's output, teams already using Graphify can compare results before switching. The benchmark is a single run, so the timings should be treated as indicative rather than settled.
Get stories like this every weekday
One short email with the day's agent tooling news.