graphicle
Code graph and memory for your coding agents, in one Rust program. For Claude Code, Codex, Cursor and any MCP client.
Runssource: GitHubhomepageRustApache-2.0commit 160fb9245d0a
Rust, Apache-2.0 licensed. The project labels itself: agent memory, ai agents, claude code, code analysis, code graph, code intelligence, code search and codex.
graphicle runs. An Argusic agent installed it in 0.1 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Graphicle 0.1.5 installed via prebuilt binary, setup completed successfully on the repository (code graph built, agent connected, hooks installed, web app serving HTTP 200), all core commands function without errors
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- under a minute
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- graphicle --version returned 'graphicle 0.1.5 (core)', graphicle setup synced 1549 files and built a code graph (18563 nodes, 51244 edges), graphicle doctor reported 0 problems, graphicle open served HTTP 200 on the web app, graphicle mcp responded to initialize via stdin/stdout, and graphicle-graph --version returned 'graphicle-graph 0.1.5'
- Model tokens used
- 82,902
- Exact commit tested
- 160fb9245d0a
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
=== Graph extract === -rw-rw-r-- 1 runner runner 20933780 Oct 23 20:18 /work/repo/.graphicle/graph.json === Web app test === Graphicle is ready at http://127.0.0.1:8857 graphicle: the app runs here until you press Ctrl-C Open this address in your browser (it signs you in once, within 3 minutes): http://127.0.0.1:8857/#session=a55e2cf2ab4445fda7f1a0ed35ccef53092790cddc0c4374842c94d02d1047d3 200 All verified. Here's the final report: tokens used 82,902 All verified. Here's the final report:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.1 minutes, faster than the median of the 19 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 20 agent-memory projects Argusic has installed and timed, graphicle was the 1st fastest to reach a running state, and 19 of 20 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.1 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-memoryai-agentsclaude-codecode-analysiscode-graphcode-intelligencecode-searchcodexcoding-agentscontext-engineeringcursordeveloper-toolsgraphragknowledge-graphlocal-firstmcpmcp-servermodel-context-protocolrusttree-sitter
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/graphicle)Questions
- Does graphicle run?
- Yes. graphicle runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test graphicle?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 160fb9245d0a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test graphicle?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does graphicle take to install?
- 0.1 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does graphicle need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing graphicle?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does graphicle compare with the alternatives?
- Of the 20 agent-memory projects Argusic has installed and timed, graphicle was the 1st fastest to reach a running state, and 19 of 20 reached one at all.
- Where is the evidence for graphicle?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.