openinterpreter
A coding agent for open models like Kimi K3 and GLM 5.3
Runs with mockssource: GitHubhomepageRustApache-2.0commit 5b07159c4779
Rust, Apache-2.0 licensed. The project labels itself: acp, coding agent, deepseek, kimi, python, qwen and rust.
openinterpreter runs, with stand-ins for the services it depends on. An Argusic agent installed it in 49 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The codex-rs workspace builds successfully, the binary launches, and the core protocols/config/otel/api tests all pass. CLI tests pass at 99.4% with only 2 pre-existing failures unrelated to the installation: features list doesn't fetch cloud config, and sandbox enforcement needs bubblewrap.
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 92 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.
- No Rust toolchain installed10 minutes
- cargo-nextest not found (required for test runner)5 minutes
- CLI test features_list_honors_cloud_managed_feature_requirements fails: features list subcommand doesn't wire up cloud config bundle loader5 minutes
- just command not found4 minutes
- CLI test app_server_rejects_invalid_code_mode_host_urls fails: http:// URLs are now valid (gRPC support)3 minutes
- Release build fails: cc compile error for tree-sitter native crate3 minutes
- Install time
- 49 minutes
- Cold machine to finish
- 71 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- Model tokens used
- 270,358
- Exact commit tested
- 5b07159c4779
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec /bin/sh -lc '# Final verification . "$HOME/.cargo/env" && cd /work/repo/codex-rs && echo "Binary exists:" && ls -la target/debug/code… succeeded in 0ms: Binary exists: -rwxrwxr-x 2 runner runner 1302143600 Sep 5 22:51 target/debug/codex Version: codex 0.0.40 Binary runs: OK tokens used 270,358
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
- Installed in 49 minutes.
- Recovered from all 8 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
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 | 1/3 | Runs with mocks | 92.00 | 0.29 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.12 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.12 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openinterpreter)Questions
- Does openinterpreter run?
- openinterpreter runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 49 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test openinterpreter?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5b07159c4779. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test openinterpreter?
- The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does openinterpreter take to install?
- 49 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 openinterpreter need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing openinterpreter?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for openinterpreter?
- All 3 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.