Graphicle: Code Graph and Memory for Coding Agents

Quick start

Three commands.

graphicle setup indexes the repository, builds its code graph and connects the coding agents it finds. It lists every file it changes and backs each one up first; graphicle disconnect undoes it all.

Works with Claude Code, Cursor, Codex, VS Code, Claude Desktop and any MCP client. macOS and Linux.

brew install graphicle-ai/tap/graphicle
cd your-repo
graphicle setup

No Homebrew?

curl -fsSL https://github.com/graphicle-ai/graphicle/releases/latest/download/install.sh | sh

Why Graphicle

One program, not a stack.

The code graph, the memory, one MCP server, the web app and the command line come in one install, with one SQLite file. No Python, Docker or database server.

Native and fast

One Rust program.

On Django, a pre-release build of its engine ran a code-only extract in 7.5 s, against 72.8 s for Graphify 0.9.77, and built the same graph.

Context

Context, not re-reading.

Your agent asks Graphicle and gets the relevant code, docs and decisions as cited excerpts, within a token budget.

Citations

Answers you can check.

Every excerpt names its file and lines. Memories an agent proposes wait for your approval.

Local

Local and private.

No account and no telemetry. Nothing leaves your machine unless you ask.

Speed

Native speed.

A pre-release build of the engine against Graphify 0.9.77, both building the same graph. The released engine has no published timing yet. Method and every run.

Django, about 54,000 nodes

Seconds · shorter is faster

Seconds to build the Django code graph, Graphicle against Graphify 0.9.77. Shorter is faster.
Code-only extract
Graphicle pre-release build	7.5 s
Graphify 0.9.77	72.8 s
Update after one added definition
Graphicle pre-release build	9.8 s
Graphify 0.9.77	107.9 s

Medians of five alternating runs, start-up included, one shared Linux host, 8 workers, 8 October 2026. Both built the same graph. The released engine has no published timing yet.

How it works

Sync, recall, remember.

Your project

CodeFiles, functions, classes, calls and imports
DocumentsREADMEs, notes and decisions, versioned
Agent sessionsFinished turns, captured with credentials redacted

One program, on your machine

graphicleone command, one data folder

Code graphBuilt on every sync; recall uses it to pull in related code, such as callers

MemoryCited excerpts from every source. Agents propose memories; you approve them.

Where you use it

MCPYour coding agentsMCP tools: cited context and your reviewed memories
CLIgraphicle askCited evidence, or an answer from a model you set up
appgraphicle openThe graph and memory in your browser

Changed files sync before each answerNo account, no telemetry; nothing leaves your machine unless you ask

Sync
Graphicle reads the folder, respects .gitignore and skips secrets, keeps a versioned copy of each source and builds the code graph.
Recall
When your agent calls a tool, Graphicle syncs what changed, ranks excerpts from code, documents, sessions and reviewed memory, and returns them with citations. The tools call no model.
Remember
Captured sessions become sources. Memories that agents propose wait for your approval in the app.

Memory

Measured in the open.

In a comparison with seven memory systems, registered before any answer was scored and run with one open model as every system's reader and judge, a pre-release build of Graphicle trails none on three development sets. Every score, with its method and caveats.

For teams

Free and
open source.

Graphicle is free and open source under Apache-2.0, for individuals and teams alike. A commercial edition for teams is in private preview.

View on GitHub Start a discussion

Graphicle: code graph and memory for your coding agents.