runjam
One desktop for all your AI coding Agent, Claude Code, Codex CLI & Gemini CLI. Auto-detect, one-click install, unified chat, file explorer, terminal & editor. Local-first. Built with Tauri + Rust + Vue 3.
Runssource: GitHubhomepageRustMITcommit 5f8e67ac2185
Rust, MIT licensed. The project labels itself: agent, agent manager, ai agent, ai coding, claude code, codex cli, coding assistant and desktop app.
runjam runs. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Frontend builds with Vite, backend compiles with Cargo, all 98 tests (13 JS + 85 Rust) pass, and the desktop binary launches on Xvfb and starts its proxy server.
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 85 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.
- Tauri Linux system -dev packages missing (glib-2.0, gtk3, pango, cairo, webkit2gtk-4.1, javascriptcoregtk-4.1, libsoup-3.0)8 minutes
- @tailwindcss/oxide missing native binding for linux-x64-gnu2 minutes
- cargo not found (no Rust toolchain)1 minute
- Install time
- 15 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm install && vite build exited 0; vitest run: 13 passed; cargo test: 85 passed; ./runjam started and printed '[proxy] started on port 59268' on DISPLAY=:99
- Model tokens used
- 133,138
- Exact commit tested
- 5f8e67ac2185
- 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 attempt that decided the verdict above. 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.
- **`cargo build`**: compiled successfully (lib + binary, 35 warnings only) - **`cargo test`**: 85 Rust tests passed, 0 failed, 1 ignored - **Binary launch**: the binary started, printed `[proxy] started on port 59268`, and stayed up unt… tokens used 133,138 All checks passed. Here's the final report: - **`npm install`**: completed successfully (package-lock.json + 239 packages) - **`vite build`**: built successfully in 30s - **`vitest run`**: 1 file, 13 tests passed - **`cargo build`**: compiled successfully (lib + binary, 35 warnings only) - **`cargo test`**: 85 Rust tests passed, 0 failed, 1 ignored - **Binary launch**: the binary started, printed `[proxy] started on port 59268`, and stayed up unt…
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 3 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 15 minutes to install, slower than the median of the 32 comparable projects Argusic has measured.
Of the 33 agent projects Argusic has installed and timed, runjam was the 24th fastest to reach a running state, and 25 of 33 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 | Unverified | 70.00 | 0.03 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.07 |
Topics (from GitHub)
agentagent-managerai-agentai-codingclaude-codecodex-clicoding-assistantdesktop-appdeveloper-toolsgemini-clillmlocal-firstopen-sourcerustskilltaurivue3
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/runjam)Questions
- Does runjam run?
- Yes. runjam runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test runjam?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5f8e67ac2185. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test runjam?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does runjam 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 runjam need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing runjam?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does runjam compare with the alternatives?
- Of the 33 agent projects Argusic has installed and timed, runjam was the 24th fastest to reach a running state, and 25 of 33 reached one at all.
- Where is the evidence for runjam?
- 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.