rustman
Free, open-source API testing desktop app built with Rust. No account, no cloud, no telemetry.
Runssource: GitHubhomepageRustMITcommit 5fde2dc34ac0
Rust, MIT licensed. The project labels itself: api client, api testing, desktop app, developer tools, iced rs, open source, postman alternative and productivity.
rustman runs. An Argusic agent installed it in 10 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Rustman 0.3.15 builds from source on Ubuntu 24.04 with Rust 1.99.1, all 139 unit tests pass, and the GUI launches and stays up on Xvfb :99.
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, 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.
- Rust toolchain (cargo/rustc) not found in PATH1 minute
- Install time
- 10 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- cargo test exited 0, 139 passed, 0 failed, 3 ignored; binary launches and stays up on :99 under timeout
- Model tokens used
- 120,579
- Exact commit tested
- 5fde2dc34ac0
- 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.
3. **`cargo build --release`** completed in ~7m54s, producing a 23 MB binary at `target/release/rus… 4. **`cargo test`** ran all 139 tests — all passed, 0 failed, 3 ignored. 5. **GUI launch** under Xvfb (`:99`) succeeds: the process stays up until the timeout kills it. The… tokens used 120,579 Now I have all the data I need. Let me compile the final ARGUSIC_RESULT. **What happened:** 1. **Rust toolchain** was missing — installed via rustup (no root needed). 2. **System -dev packages** (libxkbcommon-dev, libxi-dev, etc.) were not present but the build succ… 3. **`cargo build --release`** completed in ~7m54s, producing a 23 MB binary at `target/release/rus… 4. **`cargo test`** ran all 139 tests — all passed, 0 failed, 3 ignored. 5. **GUI launch** under Xvfb (`:99`) succeeds: the process stays up until the timeout kills it. The…
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 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
- Took 10 minutes to install, slower than the median of the 34 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 35 api-client projects Argusic has installed and timed, rustman was the 21st fastest to reach a running state, and 20 of 35 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.
- A quick evaluation: it was running 10 minutes after the clone.
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
Topics (from GitHub)
api-clientapi-testingdesktop-appdeveloper-toolsiced-rsopen-sourcepostman-alternativeproductivityrustrust-langswagger
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/rustman)Questions
- Does rustman run?
- Yes. rustman runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test rustman?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5fde2dc34ac0. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test rustman?
- 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 rustman take to install?
- 10 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 rustman need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing rustman?
- 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 rustman compare with the alternatives?
- Of the 35 api-client projects Argusic has installed and timed, rustman was the 21st fastest to reach a running state, and 20 of 35 reached one at all.
- Where is the evidence for rustman?
- 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.