A code graph and a memory, in one local Rust binary

What it does

Graphicle maps a repository into a code graph (a Rust port of Graphify) and layers agent memory on top: project docs, decisions, and past agent sessions. It exposes both through one MCP server, so Claude Code, Cursor, Codex, VS Code, Claude Desktop or any MCP client can query it. Answers come back as cited excerpts — exact files and lines — and it runs entirely on your machine.

The interesting bit

The memory side is cheap where competitors are spendthrift: on LoCoMo-10 it matched Hindsight 0.10.2 (87.7 vs 87.3) and beat Mem0 OSS 2.2.1 (81.9) while making about 12 model calls per conversation during ingestion, versus roughly 160 and 332. The graph engine is also fast — 3.4 to 23.9 times quicker than Graphify 0.9.100 in 34 of 39 measurements, with lower peak memory in 34 of 39.

Key highlights

• One install: code graph, memory, MCP server, and a local app, all in a single Rust program
• Local-first: no API key, no account, no telemetry
• Git hooks keep the graph current after every commit; graphicle disconnect undoes everything setup touched
• graphicle ask works with no model configured — it just shows the evidence
• Bonus flow: see, pixel, and fix commands reproduce a bug with computer use, locate the drawing code, and patch it with test feedback loops

Caveats

• Windows is a preview build, x86-64 only, and not code-signed
• The memory benchmarks come from pre-release builds on development sets, with one open model as reader and judge — treat the numbers as indicative, not gospel
• The graphs differ slightly from Graphify’s (node counts within 1.6%, edges within 1.1%), and Graphify was actually faster on 5 no-change updates where it stops early

Verdict

Worth a look if you run coding agents on real repos and want grounded, cited context without shipping your code or your memory to someone else’s API. If you don’t use MCP clients or your projects are three files big, this is a hammer looking for a nail.