Graphicle-AI / graphicle

Code graph and memory for your coding agents, in one Rust program. 
 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 · Docs · Coming from Graphify? · Discussions 
## Quick start
 [code] 
 No Homebrew? curl -fsSL https://github.com/graphicle-ai/graphicle/releases/latest/download/install.sh | sh · Release archives · Other ways to install 
Windows: a preview build for x86-64, not yet code-signed (Windows (preview)). 
`graphicle setup` indexes the repository, builds its code graph and connects the coding agents it finds. It also turns on session
capture, adds a two-line section to `AGENTS.md` (unless Claude Code is the only agent) and installs Git hooks that keep the project current. It lists every file it changes and
backs each one up first; `graphicle disconnect` undoes it all.
Then ask your agent to *"use graphicle to find where failed requests are retried"*, or ask from the terminal:
 [code] 
 Real output, cut after the first excerpt. With no model configured, ask shows the evidence; graphicle config set model anthropic (or openai , ollama ) adds written answers. 
 Let your coding agent install it 
Paste this into Claude Code, Codex or Cursor:
 [code] 
## Start here
| You want to | Run |
|---|---|
| Give your coding agent the code graph and your project's memory | `graphicle setup` in the repository |
| Ask a question from the terminal | `graphicle ask "how are failed requests retried?"` |
| Browse the graph, the sources and the memory | `graphicle open` |
| See what a change to a symbol touches | `graphicle graph extract . --code-only`, then `graphicle graph affected "retry()"` |
| Check that everything works | `graphicle doctor` |
| Undo everything setup did | `graphicle disconnect` |
| Move from Graphify, or run a server for a team | Moving from Graphify · Team server |
## Why Graphicle
- **Native and fast.** One Rust program. 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 (code-only extract, priming update and update with no change, on the same machine with 3 CPUs and 8 workers each). The graphs differ slightly: node counts within 4.7%, edge counts within 2.0% (speed table). A later pre-release build with 0.1.1's memory changes, 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).
- **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,