Graphicle: code graph and project memory for agents
Graphicle
Code graph and project memory in one Rust program: the agent gets excerpts with file and line citations
- 432 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Setup edits agent configuration, adds Git hooks and turns on session capture in the project
- The index covers code, documents and conversations with the agent, and with answers turned on, excerpts go to the chosen model provider
Install
- Works in
Manual install
brew install graphicle-ai/tap/graphicle && graphicle setupRun setup in the repository root; it connects the agents it finds. Main commands: graphicle ask, graphicle graph, graphicle graph affected, graphicle open, graphicle doctor, graphicle disconnect, graphicle config set model.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Setup edits agent configuration, adds Git hooks and turns on session capture in the project
- The index covers code, documents and conversations with the agent, and with answers turned on, excerpts go to the chosen model provider
This is third-party code. Review the repository files before installing.
What it does
Graphicle parses a repository with tree-sitter, with no model, and builds a code graph of files, functions and classes with their calls and imports. Next to it, it keeps project documents (Markdown, PDF, Office files, HTML), approved decisions and past Claude Code and Codex sessions. The agent asks over MCP and receives excerpts that name the file and lines, within a token budget you set. The graphicle setup command indexes the repository and connects the agents it finds over MCP. It also turns on session capture, adds a two-line section to AGENTS.md and installs Git hooks that refresh the index after a commit, merge and checkout. Before each answer Graphicle re-reads the files changed since last time, and graphicle disconnect undoes everything setup did. graphicle ask answers a question about the code, and graphicle graph searches the graph and shows what depends on a symbol. graphicle open shows the graph and the memory in the browser, and graphicle doctor checks the installation. Memories an agent proposes wait for your approval in that web app.
Who it is for. For developers whose Claude Code, Codex or Cursor spend many steps finding the right place in a large repository.
Good fit when
- The agent spends long hunting for where failed requests are retried, and you want excerpts with file and line citations
- Before editing a function you need to know what depends on it, which graphicle graph affected shows
- You want a new session to start with approved notes and the latest turns of the previous one
- Project documents in PDF and Office should be searchable together with the code
- You work across several repositories and want shared memory for the workspace
Not a fit when
- The repository is small and the agent finds things with plain search: the author does not promise token savings
- Agent configuration files must stay untouched: setup edits .mcp.json and the Codex, Cursor and VS Code settings
- You need a signed, verified Windows build: the Windows version is a preview and not code-signed
- You rely on very long sessions with memory built up over time: the author has not tested such cases yet
Example request
Use graphicle to find where failed requests are retried in the project, and show the files and lines.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
The Windows x86-64 build is a preview and is not code-signed. Setup changes the configuration of the clients it finds and installs Git hooks, so review the list of changed files right after installation.
Graphicle runs locally, with no account and no telemetry, and goes online on its own only once a day to check for a new release. Written answers require choosing a model with graphicle config set model, after which excerpts go to the chosen provider: Anthropic, OpenAI or local Ollama.
In the author's measurements Graphicle finds code as well as plain search, and the author does not claim token savings. Whether the releases and the project site are reachable from Russia has not been checked.
How to disable. Run graphicle disconnect: it removes the entries and hooks it added to client configuration, and the .graphicle-bak copies remain.
FAQ
How do I install Graphicle for Claude Code?
Run brew install graphicle-ai/tap/graphicle, then graphicle setup in the repository root. For Claude Code the entry goes into the project's .mcp.json and the session capture hooks into .claude/settings.local.json.
Which agents connect automatically?
Setup finds Claude Code, Codex, Cursor, VS Code and Claude Desktop and connects them over MCP. Any other MCP client can use a short JSON entry, and the MCP documentation has an example.
Does Graphicle send code out?
No, unless you ask it to. The graph and memory live in one SQLite file on your machine, and the MCP tools call no model.
How does Graphicle differ from Graphify plus a memory server?
It combines the code graph, memory and MCP in one install with one storage file. A two-tool setup needs separate configuration of each agent and two MCP servers.
How do I turn off the update check?
Set the environment variable GRAPHICLE_NO_UPDATE_NOTIFIER=1. After that Graphicle stops going online on its own.
Discussion
No questions or reviews yet.
Related
MCP serversCodeGraph (Rust)
codegraph-rust
A Rust code graph for agents: four MCP tools show what an edit will touch, how the architecture fits together and where the fragile spots are
The /graphify skill builds a knowledge graph of a project's code, docs and PDFs so the agent queries the graph instead of grepping
Local code graph for agents: an MCP server returns entry points, symbol links and change impact in one call
Local code structure graph: builds a repository map with tree-sitter and serves the assistant only the context a change actually touches over MCP
An MCP server and CLI that build a knowledge graph of a monorepo and let an agent query, understand and edit multi-language code
Deep Graph MCP: a code graph of a repository for agents
Deep Graph MCP
An MCP server that gives an agent a repository code graph: search by meaning, symbol links and the places an edit would touch
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Graphicle: code graph and project memory for agents (this entry) | no | not required | 432 | |
| graphify | no | 138,535 | a Python code-graph tool only; memory comes from a separate server | |
| code-review-graph | no | not required | 32,487 | a code graph for reviewing changes, with no shared project memory |
| CodeGraph | no | not required | 75,918 | a code graph for the agent, without documents or session memory |
README in short
The documentation opens with speed measurements on 13 codebases and fact-finding accuracy, which the author labels as pre-release results. Separate sections explain the three-step method and compare the install with a pair of a code-graph tool and a memory server.