craft-anything

Craft Anything: understand how any software works, and craft your own.

Runssource: GitHubRustApache-2.0commit 5a45b3cd7811

Rust, Apache-2.0 licensed.

craft-anything runs. An Argusic agent installed it in 3.4 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Craft Anything CLI 0.4.0 is installed and doctor reports healthy, the desktop app opens a live window on Xvfb, and the full workspace test suite passes with 1622 tests and no failures.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.32 (measured)
recorded runs
1
last tested
stars
4,984
forks
0
open issues
0
watchers
0
created
-
last push
-

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.

Time lost to each failure while testing craft-anything, 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.

  • rustc and cargo were not installed in the container0.1 minutes
  • cargo fmt --all --check failed because rustfmt was not installed in the minimal toolchain0.1 minutes
  • cargo clippy failed because clippy was not installed in the minimal toolchain0.1 minutes
  • The wasm32-unknown-unknown target was absent for cargo xtask wasm0.1 minutes
Install time
3 minutes
Cold machine to finish
49 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
cargo test --locked --workspace exited 0 with 1622 passed, 0 failed, 9 ignored across 41 test binaries; craft-anything-cli doctor exited 0 with healthy true and MCP protocol 2025-06-18 with 29 tools; craft-anything launched on DISPLAY=:99 as window 0x200002 Craft Anything and stayed running
Model tokens used
359,731
Exact commit tested
5a45b3cd7811
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.

- Built the desktop app with `cargo build --locked --release -p craft-anything`; it exited 0 and pr…
- Added the missing `rustfmt`, `clippy`, and `wasm32-unknown-unknown` rustup components; all subseq…
**Verified**
- `craft-anything-cli --version` printed `craft-anything-cli 0.4.0`.
- `craft-anything-cli doctor --output-format json` exited 0 with `"healthy":true`, 23 checks (3 ok,…
- The GUI opened window `0x200002 "Craft Anything"` on `DISPLAY=:99`, stayed running at 1280x800, a…
- Deep triage identified the installed CLI binary as x86_64 ELF/Linux, entry `0x597d00`; `native-fu…
- `cargo test --locked --workspace` exited 0: **1,622 passed, 0 failed, 9 ignored** across 41 test …
- `cargo clippy ... -- -D warnings`, `cargo fmt --all --check`, `cargo xtask layers`, `cargo xtask …
**Not verified**
- No live AI rebuild: `claude` is absent and `doctor` reports no AI backend. I did not invent crede…
- The README’s Debian development packages were absent, but the project built and launched using th…

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.
  • Installed in 3.4 minutes, faster than the median of the 16 comparable projects Argusic has measured.
  • Recovered from all 4 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.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 17 Rust projects Argusic has installed and timed, craft-anything was the 3rd fastest to reach a running state, and 15 of 17 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 3.4 minutes after the clone.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.32

Embed the badge

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

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

Questions

Does craft-anything run?
Yes. craft-anything runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test craft-anything?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5a45b3cd7811. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test craft-anything?
The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does craft-anything take to install?
3.4 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 craft-anything need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing craft-anything?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does craft-anything compare with the alternatives?
Of the 17 Rust projects Argusic has installed and timed, craft-anything was the 3rd fastest to reach a running state, and 15 of 17 reached one at all.
Where is the evidence for craft-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.

Discussion