Ataru
High-performance AI memory retrieval for local agent history, a Rust search core (SDK / API / JSON CLI) plus a desktop GUI. Tantivy + Jieba keyword search, optional semantic recall, stable Turn/Run/Session/Project IDs.
Runssource: GitHubhomepageRustApache-2.0commit 44ad0d435d50
Rust, Apache-2.0 licensed. The project labels itself: agent memory, ai memory, ai tools, claude code, desktop app, full text search, local first and memory retrieval.
Ataru runs. An Argusic agent installed it in 9 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Rust binary ataru 0.41.6 builds, passes 34 unit tests, and responds to CLI subcommands (version, index status). Frontend TypeScript type-checks cleanly and Vite production build outputs dist/index.html. The Rust binary has zero unresolved shared library dependencies on ldd.
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Missing GTK/WebKit dev libraries (glib, gtk3, webkit2gtk-4.1, pango, cairo, etc.)5 minutes
- Missing runtime shared libraries for linking (harfbuzz, cairo-gobject, libxslt, gstreamer, etc.)2 minutes
- Node 18.19.1 too old for Vite 7 (crypto.hash not a function)2 minutes
- Rust toolchain not installed1 minute
- pnpm not available on PATH1 minute
- esbuild native binary not built (pnpm ignored build scripts)1 minute
- Install time
- 9 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- cargo test in src-tauri reported '34 passed, 0 failed'; /work/repo/src-tauri/target/debug/ataru --version returned 'ataru 0.41.6'; /work/repo/src-tauri/target/debug/ataru index status --json returned valid JSON with state:idle; npx tsc --noEmit exited 0; npx vite build produced dist/index.html successfully
- Model tokens used
- 557,829
- Exact commit tested
- 44ad0d435d50
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
export C_INCLUDE_PATH=/tmp/usr/usr/include export LIBRARY_PATH=/tmp/usr/usr/lib/x86_64-linux-gnu cd /work/repo/src-tauri && cargo test 2>&1 | grep -E "test result|ok'"\\.\" | head -5" in /work/repo succeeded in 818ms: test result: ok. 34 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.62s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Here is the final report: tokens used 557,829 Here is 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.
- Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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
- Took 9 minutes to install, slower than the median of the 27 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 28 agent-memory projects Argusic has installed and timed, Ataru was the 19th fastest to reach a running state, and 24 of 28 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 9 minutes after the clone.
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-memoryai-toolsclaude-codedesktop-appfull-text-searchlocal-firstmemory-retrievalragreactrustsearch-enginesemantic-searchtailwindcsstantivytauritypescriptvector-search
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ataru)Questions
- Does Ataru run?
- Yes. Ataru runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test Ataru?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 44ad0d435d50. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Ataru?
- The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Ataru take to install?
- 9 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 Ataru need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Ataru?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Ataru compare with the alternatives?
- Of the 28 agent-memory projects Argusic has installed and timed, Ataru was the 19th fastest to reach a running state, and 24 of 28 reached one at all.
- Where is the evidence for Ataru?
- 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.