Graphicle: code graph and memory for your coding agents.
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. It runs on your machine.
Open source · Apache-2.0 · Version 0.1.18 · 591 GitHub stars
brew install graphicle-ai/tap/graphicle
cd your-repo
graphicle setupNo Homebrew?
curl -fsSL https://github.com/graphicle-ai/graphicle/releases/latest/download/install.sh | shirm https://github.com/graphicle-ai/graphicle/releases/latest/download/install.ps1 | iexIn PowerShell. Then open a new terminal and run graphicle setup in your repository. A preview build for x86-64, not yet code-signed. Windows notes
graphicle setup indexes the repository and connects the coding agents it finds, backing up every file it changes; graphicle disconnect undoes it all. Works with Claude Code, Cursor, Codex, VS Code, Claude Desktop and any MCP client.
One program, not a stack.
The code graph, the memory, one MCP server, the web app and the command line come in one install. No Python, Docker or database server.
Graphicle, or a code-graph tool plus a memory server
| A code-graph tool + a memory server | Graphicle | |
|---|---|---|
| Install | Two tools, often on different runtimes, and often a database server | One install |
| Connect your agents | Configure each tool in each agent | One command, graphicle setup |
| MCP servers in your agent | Two, configured separately | One, with the graph and the memory tools |
| Storage | Graph files plus the memory server's database | One SQLite file in one data folder |
| Code structure: calls, imports, impact | The graph tool | graphicle graph |
| Docs, decisions, past sessions | The memory server | Built in |
| Citations and review | Varies | A file and its lines on every excerpt; agent memories wait for approval |
The left column is a code-graph tool, such as Graphify's open-source engine, plus a separate memory server. It is not a comparison with Graphify Cloud, a hosted service that includes memory. Graphicle against Graphify, Mem0, Hindsight and others
Memory, without a separate memory server.
It runs in the same program as the code graph. Its memory library adapts parts of open-source memory systems, among them Hindsight, Mem0 and Graphiti, credited in its notices.
Cited context, within a budget you set
Your agent asks Graphicle and gets the relevant code, docs and decisions as cited excerpts, within a token budget you set. In our tests it tied grep on finding code, and we do not claim it saves tokens. What we measured
Project memory
Docs (Markdown, PDF, Office, HTML), reviewed decisions and procedures, and past Claude Code and Codex sessions, searchable alongside the code.
Tied to your code
A reviewed memory is tied to the function it is about, and goes stale when that code changes. In a 30-note sample, the 15 notes whose function changed were flagged and no other; a wider exploratory check found some false flags. Details and limits
Sessions carry over
Session capture keeps each finished turn, and once you have reviewed memories, each new session starts with them and the latest turns.
Forgetting with a receipt
Deleting a memory or a captured session also removes what was derived from it, and you get a hash-chained deletion receipt.
Local and private
No account and no telemetry: your code and data leave your machine only when you ask. The only automatic request is a check for a new release, at most once a day, which GRAPHICLE_NO_UPDATE_NOTIFIER=1 turns off. Recall and session capture need no model or API key; proposing memories from sources uses one, and local models through Ollama work. Privacy details
Against seven memory systems.
Graphicle and seven memory systems answered the same questions, under a protocol written before any answer was scored. Graphicle against each one
LoCoMo-10, 1,540 questions
Accuracy, points out of 100 · higher is better
| System | Accuracy |
|---|---|
| Graphicle | |
| Hindsight | |
| Mem0 OSS | |
| MemMachine | |
| Honcho | |
| Cognee | |
| Graphiti | |
| Mastra OM |
- 13 of 21registered comparisons Graphicle led, across three development sets; 4 ties, none behind
- 12 vs 160 vs 332estimated model calls per conversation while ingesting LoCoMo-10: Graphicle, Hindsight 0.10.2, Mem0 OSS 2.2.1
- 43K vs 1.14M vs 3.18Mestimated prompt tokens per conversation in the same runs
A pre-release comparison with seven memory systems: development sets; one open model as every system's reader, judge and model; a pre-release build of Graphicle, not its released defaults. These scores cannot be set against any vendor's published numbers, and the call counts per conversation are estimates. Of the 21 registered comparisons, 3 led without meeting every condition of the rule and 1 was not run. Every score, with its method and caveats. The early pre-release evaluations on GPT models, wins and losses, are on the comparison page.
Native speed.
On 13 codebases, Graphicle's 0.1.1 memory engine (a pre-release build) took 3.0 to 22.7 times less time than Graphify 0.9.91 in all 39 measurements: a code-only extract, a priming update and an update with no change on each. Every measurement. A later pre-release build, whose graphs also differ from Graphify's, used less peak memory than Graphify 0.9.91 in all 39 measurements, from 0.29 to 0.97 times Graphify's figure (memory table).
Code-only extract, 13 codebases
Graphify 0.9.91's time ÷ Graphicle's · higher is less time
| Codebase | Times less time |
|---|---|
| kubernetes | |
| rails | |
| flask | |
| prometheus | |
| react | |
| scikit-learn | |
| pandas | |
| vscode | |
| ripgrep | |
| tokio | |
| redis | |
| next.js | |
| spring-boot |
Finding the files a fix changes.
Offline ranking, 100 SWE-bench Verified issues never used for tuning. Graphicle 0.1.3 put a file the fix changed in its first 5 files for 75 issues, against 61 for BM25 (SWE-bench style), a significant difference (McNemar exact p = 0.013); for the first file (43 vs 35) and the first 10 (82 vs 77) the differences are not significant. This measures ranking, not whether a coding agent fixes more issues; the agent test of 0.1.3 is pending. Method, task lists and limits
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
Where you use it
- MCPYour coding agentsMCP tools: cited context and your reviewed memories
- CLI
graphicle askCited evidence, or an answer from a model you set up - app
graphicle openThe graph and memory in your browser
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.
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.