rust-anything
Rewrite your whole app in Rust, one piece at a time, checked against the original's recorded behavior at every step. CLIs, HTTP servers and libraries in TypeScript, Python, C, Go, Ruby and Java.
Runs with mockssource: GitHubRustMITcommit a3f40af356ab
Rust, MIT licensed. The project labels itself: agent skills, claude code, cli, code migration, codex, ffi, golang and java.
rust-anything runs, with stand-ins for the services it depends on. An Argusic agent installed it in 41 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
rust-anything 2.1.0 builds, installs, and runs; the binary answers its help and version commands; the unit test suite passes 192/193 (the one failure is Node 18 being too old to run .ts files directly, needs 22.6+); all 18 app integration tests, all 11 HTTP integration tests, and all 17 analyze tests pass; the MCP server answers with 16 tools; the doctor command reports all runtime statuses correctly.
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. 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.
- Node.js 18.19.1 (container default) cannot run .ts files directly; rust-anything needs Node 22.6+ for TypeScript execution. This caused 19 test failures across unit and integration tests (1 unit: node_writes_profile_to_a_temp_path_with_spaces; 10 loop tests; 4 native tests; 2 recording tests; 1 record_timeout test; 1 untyped_js_types test; plus http had 1 transient port-contention failure)
- Optional language runtimes missing (Go, Ruby, Java, Kotlin, PHP, .NET) — tests that depend on them were skipped automatically.
- Install time
- 41 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- rust-anything --version returned 'rust-anything 2.1.0'; cargo build exits 0; cargo test --lib: 192 passed, 1 failed (Node 18 limitation); cargo test --test app: 18/18 passed; cargo test --test analyze: 17/17 passed; cargo test --test http: 11/11 passed; cargo test --test effects: 3/3 passed; cargo test --test library: 4/5 passed (1 TS skip); cargo install --path .: installed successfully to /home/runner/.cargo/bin/rust-anything
- Model tokens used
- 152,746
- Exact commit tested
- a3f40af356ab
- 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
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.
exec /bin/sh -lc '. "$HOME/.cargo/env" && cd /work/repo && cargo test --test loop 2>&1 | grep "FAILED'"\… succeeded in 6255ms: test benchmark_awaits_async_typescript_calls_and_counts_rejections ... FAILED test classes_are_bridged_recorded_and_replayed ... FAILED test record_and_diff_catch_a_behavior_change ... FAILED test record_follows_bundler_style_imports ... FAILED test record_prefers_an_exact_tsconfig_alias_to_a_matching_wildcard ... FAILED All loop failures are the Node 18 TS issue. Now I have a comprehensive understanding. Let me produc… tokens used 152,746 All loop failures are the Node 18 TS issue. Now I have a comprehensive understanding. Let me produc…
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
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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.
- Took 41 minutes to install, slower than the median of the 126 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 127 agent-skills projects Argusic has installed and timed, rust-anything was the 125th fastest to reach a running state, and 95 of 127 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.09 |
Topics (from GitHub)
agent-skillsclaude-codeclicode-migrationcodexffigolangjavajavascriptmcpmigrationnapiperformanceportingpyo3pythonrewriterubyrusttypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/rust-anything)Questions
- Does rust-anything run?
- rust-anything runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 41 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test rust-anything?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a3f40af356ab. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test rust-anything?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does rust-anything take to install?
- 41 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 rust-anything need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing rust-anything?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does rust-anything compare with the alternatives?
- Of the 127 agent-skills projects Argusic has installed and timed, rust-anything was the 125th fastest to reach a running state, and 95 of 127 reached one at all.
- Where is the evidence for rust-anything?
- 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.