microduck
A Tiny biped duck robot 🦆
Runssource: GitHubRustApache-2.0commit a9ec4b2079ef
Rust, Apache-2.0 licensed.
microduck runs. An Argusic agent installed it in 45 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Microduck Rust workspace compiles and all 1515 tests pass on x86_64 Linux without hardware, network or root privileges, using locally extracted -dev libraries and synthetic pkg-config files to satisfy the glib/GStreamer/libudev build dependencies.
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. 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.
- Missing -dev packages: libudev-dev, libglib2.0-dev, libgstreamer1.0-dev, libgstreamer-plugins-base1.0-dev, libgstreamer-plugins-bad1.0-dev - no root access to apt20 minutes
- Linker could not find -ludev (broken symlinks in extracted -dev packages)5 minutes
- Missing rustc toolchain - none installed3 minutes
- mediad test failed at runtime: missing libdw.so.1, liborc-0.4.so.03 minutes
- Install time
- 45 minutes
- Cold machine to finish
- 38 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- cargo test --workspace exited 0: 1515 passed, 0 failed, 18 ignored; cargo build --workspace succeeded; robotctl --version printed 0.15.0; mediad --help printed usage
- Model tokens used
- 442,896
- Exact commit tested
- a9ec4b2079ef
- 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.
- **`duckctl --help`** prints all commands tokens used 442,896 The report has been printed. All tasks are complete. - **Rust** installed via rustup (1.98.1) - **C -dev headers** extracted from downloaded `.deb` packages into local prefixes - **pkg-config** synthetic `.pc` files created for libpcre2-8, libffi, zlib, orc-0.4, libunwind, li… - **Broken symlinks** in extracted `.so` files fixed - **1515 tests pass**, 0 failures, 18 ignored - **`robotctl --version`** prints `0.15.0` - **`mediad --help`** prints usage - **`duckctl --help`** prints all commands
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 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
- Took 45 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 Rust projects Argusic has installed and timed, microduck was the 4th fastest to reach a running state, and 4 of 4 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.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/microduck)Questions
- Does microduck run?
- Yes. microduck runs. Argusic installed and launched it on a clean machine in 45 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test microduck?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a9ec4b2079ef. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test microduck?
- The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does microduck take to install?
- 45 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 microduck need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing microduck?
- 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 microduck compare with the alternatives?
- Of the 4 Rust projects Argusic has installed and timed, microduck was the 4th fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for microduck?
- 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.