cocoindex
Incremental engine for long horizon agents 🌟 Star if you like it!
Runssource: GitHubhomepageRustApache-2.0commit f1c1ba4a83d3
Rust, Apache-2.0 licensed. The project labels itself: agentic data framework, ai, ai agents, change data capture, codebase intelligence, context engineering, data engineering and data indexing.
cocoindex runs. An Argusic agent installed it in 8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Python package builds and installs from source, the CLI runs and prints version 999.0.0, 1095 Python tests pass (core engine, ops, resources, connectors that don't need external services), and 144 Rust tests pass across the core, utils, and SDK crates.
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.
- cargo test for pyo3-dependent crates (cocoindex_py, cocoindex_py_utils) fails to link: 'unable to find library -lpython3.12'2 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- uv run pytest python/ exited 0: 1095 passed, 305 skipped. cargo test -p cocoindex_core exited 0: 106 passed. .venv/bin/cocoindex --version returned 'cocoindex version 999.0.0'. uv run mypy not run (requires full dependency group).
- Model tokens used
- 100,000
- Exact commit tested
- f1c1ba4a83d3
- 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.
4. Installed `maturin` via `pip3 install --break-system-packages maturin`
5. Built & installed the Rust extension with `uv run maturin develop`
**Verification:**
- `cocoindex --version` → `cocoindex version 999.0.0` (CLI works)
- `import cocoindex` → success, full API surface accessible
- Python tests: `1095 passed, 305 skipped, 2 warnings` in ~79s. The 305 skipped are all connector t…
- Core + ops + resources Python tests only: `698 passed, 4 skipped`
- Rust core tests: `106 passed` (cocoindex_core)
- Rust utils tests: `27 passed`
- Rust SDK/doc tests: `11 passed`
- Rust linking for pyo3-dependent crates (`cocoindex_py`, `cocoindex_py_utils`) fails because `libp…
<ARGUSIC_RESULT>{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 8, "errors…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 8 minutes.
- Recovered from all 1 error 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.
- Measured 2 times, so the result is not a one-off.
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 8 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)
agentic-data-frameworkaiai-agentschange-data-capturecodebase-intelligencecontext-engineeringdata-engineeringdata-indexingdata-processingetlhelp-wantedindexingknowledge-graphllmlong-horizon-agentpythonragreal-timerustsemantic-search
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cocoindex)Questions
- Does cocoindex run?
- Yes. cocoindex runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test cocoindex?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f1c1ba4a83d3. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test cocoindex?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cocoindex take to install?
- 8 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 cocoindex need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cocoindex?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for cocoindex?
- 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.