StackMap
Subscribe
Explore / graphicle
Graphicle-AI

graphicle

One Rust program giving coding agents a code graph plus memory of docs, decisions and past sessions, served over MCP to Claude Code, Codex, Cursor and VS Code.

509 36 Rust Apache-2.0updated yesterday
code-intelmemory
View on GitHubDispute this mapping →
Curator's take

Use it when you want code intelligence and project memory from one local install instead of a code-graph MCP plus a separate memory server. Skip it if you already run a dedicated code graph you like, or need team-shared memory. Its memory comparison against seven systems is pre-release and self-reported.

Mapped by ShipWithAI editors · links verified

Continue your stack

What teams reach for next — and why each earns a place beside graphicle. Ranked by curator confidence.

alternativealternativealternativealternativealternativecodebase-memory-mcpgortexcode-review-graphclaude-memcortexdbgraphicle
pairs wellalternativebuilt withpick a node for the why · open it from the panel
Weekly digest
README.md1 min read

Graphicle

Code graph and memory for your coding agents, in one Rust program.

License: Apache-2.0 Latest release Platforms: macOS, Linux and Windows (preview) Chat on Discord

Graphicle maps your repository into a code graph, remembers your project's docs, decisions and past agent sessions, and gives your coding agent cited excerpts from both: the exact files and lines. It runs on your machine: no API key needed, no account, no telemetry.
Works with Claude Code · Cursor · Codex · VS Code · Claude Desktop · any MCP client

Quick start · How it works · Benchmarks · Memory, compared · Docs · Coming from Graphify? · Discussions

Graphify, ported to Rust. Plus memory. Code graph and memory for your coding agents, updated after every commit. First build of Kubernetes v1.37.1, a code-only graph, one run each with 3 CPUs and 8 workers: Graphify 0.9.100 29 min 18 s, Graphicle 0.1.11 1 min 14 s, 23.9 times less time; across 13 codebases, 3.4 to 23.9 times less time in 34 of 39 measurements (first builds and updates); Graphify 0.9.100 was faster in the other 5: updates with no change, where it now stops early. Update after each commit, the median over 30 recent code commits with 4 CPUs each: prometheus 32.1 s for Graphify 0.9.100 against 4.9 s for Graphicle 0.1.11, tokio 11.9 s against 2.0 s, poetry 11.7 s against 1.6 s, 5.8 to 7.2 times less time; a graph left alone was stale at 25 to 30 of the 30 commits. Less memory: lower peak memory than Graphify 0.9.100 in 34 of 39 measurements, 0.30 to 0.96 times its figure. Plus agent memory: LoCoMo-10 87.7, level with Hindsight 0.10.2 (87.3) and above Mem0 OSS 2.2.1 (81.9), with about 12 model calls per conversation against 160 and 332. One program: code graph, memory, one MCP server and an app in one install; local, no API key, no telemetry. Labels: Graphicle 0.1.11, built from its release source, against Graphify 0.9.100 on one Linux machine, measured runs one at a time; the graphs differ slightly (node counts within 1.6%, edge counts within 1.1%); in the 5 updates where Graphify was faster, it also used less memory; agent memory from a pre-release build on development sets, with one open model as every system's reader and judge.
Graphicle 0.1.11 against Graphify 0.9.100, labelled as in the picture; every measurement and its method are in docs/benchmarks.md. The code-graph engine is a Rust port of Graphify, credited below. Graphicle