cocoindex-code
A super light-weight embedded code search engine CLI (AST based) that just works - improves speed and efficiency for coding agent 🌟 Star if you like it!
Runssource: GitHubhomepagePythonApache-2.0commit 2a3ba53b5cab
Python, Apache-2.0 licensed. The project labels itself: agents, ast, claude code, cocoindex, code search, codex, coding agent and context engineering.
cocoindex-code runs. An Argusic agent installed it in 9.3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The cocoindex-code project is fully installed and operational: uv sync completes, all 317 tests pass, and the CLI (ccc) is functional with local embeddings.
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
- 9 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- Model tokens used
- 32,012
- Exact commit tested
- 2a3ba53b5cab
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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.
│ reset Reset project databases and optionally remove settings. │
│ doctor Check system health and report issues. │
│ mcp Run as MCP server (stdio mode). │
│ version Print the CLI version. │
│ daemon Manage the daemon process. │
╰──────────────────────────────────────────────────────────────────────────────╯
Everything works. Let me produce the final JSON result.
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 9.3, "…
tokens used
32,012
Everything works. Let me produce the final JSON result.
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 9.3, "…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.
- 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
- Took 9.3 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 8 agents projects Argusic has installed and timed, cocoindex-code was the 8th fastest to reach a running state, and 5 of 8 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.3 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)
agentsastclaude-codecocoindexcode-searchcodexcoding-agentcontext-engineeringcontext-windowcontext-window-optimizationindexingmcpopen-codepythonrusttree-sitter
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cocoindex-code)Questions
- Does cocoindex-code run?
- Yes. cocoindex-code runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test cocoindex-code?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2a3ba53b5cab. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test cocoindex-code?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cocoindex-code take to install?
- 9.3 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-code need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cocoindex-code?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does cocoindex-code compare with the alternatives?
- Of the 8 agents projects Argusic has installed and timed, cocoindex-code was the 8th fastest to reach a running state, and 5 of 8 reached one at all.
- Where is the evidence for cocoindex-code?
- 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.