quivr
An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search, alerts, and plugins for formats, models and business rules.
Runssource: GitHubhomepageGoMITcommit f247cb21bbec
Go, MIT licensed. The project labels itself: ai, api, chatbot, chatgpt, database, docker, framework and frontend.
quivr runs. An Argusic agent installed it in 10.6 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Quivr V2 repository installs and builds with Go 1.27.1. All non-Docker checks pass: Go vet, Go tests (43 packages), Python scripts tests (219), Python eval tests (198/199), documentation validation, contract validation (OpenAPI + 240 plugin fixtures), denylist check, migration ordering, image context check, plugin boundary check, and both Python and Go plugin SDK certifications (5 first-party plugins).
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 96 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.
- PyYAML and other Python deps missing for docs/contracts checks5 minutes
- Python eval tests failed: ModuleNotFoundError for jev_rerank3 minutes
- git origin/main not fetched, docs check needed it1 minute
- Go 1.27.1 not installed in container0.5 minutes
- Python tests (test_ci_output, test_image_context) failed with 'go: not found'0.5 minutes
- Docker unavailable for client SDK generation (openapi-generator)
- Install time
- 11 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- go test ./... all 43 Go packages passed; python3 -m unittest discover -s scripts, 219/219 passed; all 5 plugin SDK checks certified; go vet ./... clean; three binaries build successfully
- Model tokens used
- 397,895
- Exact commit tested
- f247cb21bbec
- 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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
All core checks pass. Let me compile the final result. exec /bin/sh -lc 'echo "Start time estimate:" && date -d "2026-11-02T01:37:00Z" +%s && echo "End time:" … succeeded in 0ms: Start time estimate: 1793583420 End time: 1793584058 All checks pass comprehensively. Let me compile the final report. tokens used 397,895 All checks pass comprehensively. Let me compile 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 MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 10.6 minutes to install, slower than the median of the 234 comparable projects Argusic has measured.
Of the 235 ai projects Argusic has installed and timed, quivr was the 173rd fastest to reach a running state, and 167 of 235 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.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.15 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.24 |
Topics (from GitHub)
aiapichatbotchatgptdatabasedockerframeworkfrontendgroqhtmljavascriptllmopenaipostgresqlprivacyragreactsecuritytypescriptvector
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/quivr)Questions
- Does quivr run?
- Yes. quivr runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test quivr?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f247cb21bbec. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test quivr?
- The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does quivr take to install?
- 10.6 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 quivr need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing quivr?
- 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 quivr compare with the alternatives?
- Of the 235 ai projects Argusic has installed and timed, quivr was the 173rd fastest to reach a running state, and 167 of 235 reached one at all.
- Where is the evidence for quivr?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.