OpenResearch
Turn your coding agents into research agents
Runssource: GitHubRustMITcommit f336b121525d
Rust, MIT licensed.
OpenResearch runs. An Argusic agent installed it in 15 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 orx CLI v0.2.13 builds, passes all 969 tests, prints the correct version and build channel, starts the dashboard on 127.0.0.1:4791 (HTTP 200), and lists local projects with no 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. 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.
- ssh-keygen not found in container (missing openssh-client package)4 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- cargo test --locked passed 955 unit tests + 9 compute_cli tests + 5 logs_cli tests = 969 total; dashboard at http://127.0.0.1:4791 answered HTTP 200; orx version printed 'orx 0.2.13' and --build-channel printed 'development'
- Model tokens used
- 154,118
- Exact commit tested
- f336b121525d
- 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.
/bin/sh -lc 'cd /work/repo && . "$HOME/.cargo/env" && ./target/debug/orx projects --no-telemetry 2>… succeeded in 0ms: No local projects found. Run `orx up` in a repository to add one. exec /bin/sh -lc 'echo "Total tests passed: 955 unit + 9 compute_cli + 5 logs_cli = 969"; date -u +%s' i… succeeded in 0ms: Total tests passed: 955 unit + 9 compute_cli + 5 logs_cli = 969 1790753369 All 969 tests pass, the binary builds and runs, and the dashboard serves HTTP 200. Here's the summa… tokens used 154,118 All 969 tests pass, the binary builds and runs, and the dashboard serves HTTP 200. Here's the summa…
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 15 minutes, faster than the median of the 7 comparable projects Argusic has measured.
- 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 MIT, 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 8 Rust projects Argusic has installed and timed, OpenResearch was the 4th fastest to reach a running state, and 8 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.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openresearch)Questions
- Does OpenResearch run?
- Yes. OpenResearch runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test OpenResearch?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f336b121525d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test OpenResearch?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OpenResearch take to install?
- 15 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 OpenResearch need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OpenResearch?
- 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.
- How does OpenResearch compare with the alternatives?
- Of the 8 Rust projects Argusic has installed and timed, OpenResearch was the 4th fastest to reach a running state, and 8 of 8 reached one at all.
- Where is the evidence for OpenResearch?
- 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.