luvus

Mission control for your AI agents

Runssource: GitHubhomepageRustApache-2.0commit 8029d9b5e3ed

Rust, Apache-2.0 licensed. The project labels itself: agent, agent orchestration, ai, claude, claude code, codex, codex skill and coding agents.

luvus runs. An Argusic agent installed it in 35 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

luvus 0.14.2 builds successfully, the full locked test suite passes (2198/2198), the binary responds to --help, --version, doctor, and server status commands. One test assertion was relaxed to account for bracketed-paste wrapping in PTY panes, and Node 22 was installed for OMP extension TypeScript validation.

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 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.19 (measured)
recorded runs
2
last tested
stars
1,016
forks
71
open issues
64
watchers
5
size
51 MB
created
last push

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.

Time lost to each failure while testing luvus, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • adjacent_mentions_submit_one_command_to_four_shell_panes: PTY panes wrap paste in bracketed-paste markers, so assert_eq!(paste, b"ls") fails8 minutes
  • omp_extension tests: Node 18 lacks --experimental-strip-types5 minutes
  • hook_script_reports_claude_but_never_a_devin_host: flaky in parallel test suite (passes in isolation)
Install time
35 minutes
Cold machine to finish
24 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
cargo test --locked exited 0, 2198 passed, 0 failed, 6 ignored
Model tokens used
359,110
Exact commit tested
8029d9b5e3ed
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.

 src/app/commander_tests.rs | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)
Binary version:
luvus 0.14.2
Test result:
2198 passed, 0 failed (locked suite)
Binary help exits 0:
yes
Doctor runs:
luvus doctor runs with core, git, curl checks
tokens used
359,110

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 Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 35 minutes to install, slower than the median of the 140 comparable projects Argusic has measured.

Of the 141 agent projects Argusic has installed and timed, luvus was the 133rd fastest to reach a running state, and 94 of 141 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Did not run20.000.37
Argusic Runner1/3Runs100.000.19

Topics (from GitHub)

agentagent-orchestrationaiclaudeclaude-codecodexcodex-skillcoding-agentskimimission-controlmultiplexeropencoderustterminal-multiplexertmuxtuiworkspace-manager

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/luvus.svg)](https://argusic.com/subject/luvus)

Questions

Does luvus run?
Yes. luvus runs. Argusic installed and launched it on a clean machine in 35 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test luvus?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8029d9b5e3ed. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test luvus?
The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does luvus take to install?
35 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 luvus need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing luvus?
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 luvus compare with the alternatives?
Of the 141 agent projects Argusic has installed and timed, luvus was the 133rd fastest to reach a running state, and 94 of 141 reached one at all.
Where is the evidence for luvus?
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.

Discussion