umadev

UmaDev: A coding agent that works like a real dev team, commanding the Claude Code / Codex / OpenCode you already use.

Runs with mockssource: GitHubhomepageRustMITcommit 4fe51fa2cd67

Rust, MIT licensed. The project labels itself: agents, ai, ai agents, ai coding, claude code, codex cli, coding and coding agent.

umadev runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The Rust project builds, all 1466 unit/integration tests pass, the umadev binary runs and responds to --help, --version, doctor, init, and ci subcommands from a source build with no external API keys.

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

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
1
last tested
stars
267
forks
65
open issues
24
watchers
2
size
134 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.

Install time
2 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
cargo test --workspace exited 0, 1466 passed; ./target/debug/umadev --version returned 'umadev 1.1.1'; ./target/debug/umadev doctor exited 0 with 17 passed, 2 warning, 0 failed; ./target/debug/umadev ci ran governance scan across 336 files; ./target/debug/umadev init wrote workspace manifest successfully
Model tokens used
124,544
Exact commit tested
4fe51fa2cd67
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
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.

  spec: UMADEV_HOST_SPEC_V1 | level: L3 | profile: standard | slug: tmp
Next steps:
  umadev                          # launch the TUI (recommended)
  umadev run "<requirement>"      # or scripted / CI form
Inside the TUI:
  /claude /codex /opencode /grok /kimi
                                 switch base CLI (each uses its OWN login + model)
  /status                      show the active base and its driving model
The build and test suite both succeed cleanly (1466 tests pass, 0 fail). The binary runs, reports i…
tokens used
124,544
The build and test suite both succeed cleanly (1466 tests pass, 0 fail). The binary runs, reports i…

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 2 minutes, faster than the median of the 40 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Licensed MIT, as reported by its host.

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.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 41 agents projects Argusic has installed and timed, umadev was the 9th fastest to reach a running state, and 29 of 41 reached one at all.

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 Runner1/3Runs with mocks92.000.03

Topics (from GitHub)

agentsaiai-agentsai-codingclaude-codecodex-clicodingcoding-agentcoding-agentsopen-coderagrustrust-agentrust-langtuivibe-coding

Embed the badge

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

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

Questions

Does umadev run?
umadev runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test umadev?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4fe51fa2cd67. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test umadev?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does umadev take to install?
2 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 umadev need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing umadev?
Nothing did, in the recorded run: zero errors between clone and running.
How does umadev compare with the alternatives?
Of the 41 agents projects Argusic has installed and timed, umadev was the 9th fastest to reach a running state, and 29 of 41 reached one at all.
Where is the evidence for umadev?
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.

Discussion