hummingbird
[mirror] Modern music player written in Rust using GPUI with a focus on design and performance
Runssource: GitHubhomepageRustApache-2.0commit 15835949458d
Rust, Apache-2.0 licensed. The project labels itself: gpui, music player and rust.
hummingbird runs. An Argusic agent installed it in 30 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Hummingbird v0.4.0-dev builds with release profile, binary runs showing version/help, and all 549 unit tests pass on Ubuntu 24.04 x86_64.
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.
- Missing -dev packages for Linux system libraries (alsa, xkbcommon, x11, pulse, fontconfig, pipewire, dbus, wayland, xcb, zlib, png, brotli, expat)5 minutes
- Missing libclang for bindgen crate (libpipewire/spa FFI generation)5 minutes
- Linker could not find native .so files (broken symlinks in dev packages)2 minutes
- No Rust toolchain installed in container1 minute
- Missing lld-18 linker used by cargo1 minute
- Install time
- 30 minutes
- Cold machine to finish
- 37 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- cargo test exited 0, 549 passed 0 failed; target/release/hummingbird --help printed version 0.4.0-dev and usage info
- Model tokens used
- 477,739
- Exact commit tested
- 15835949458d
- 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
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 2, 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.
5. **Broken `.so` symlinks** — copied runtime `.so` files from `/usr/lib` into the extracted lib di… The final binary at `target/release/hummingbird` starts, prints version `0.4.0-dev (1583594)`, hand… tokens used 477,739 The build and all 549 tests pass. Let me compile the final report. **Errors encountered and fixed:** 1. **No Rust toolchain** — installed via `rustup` 2. **Missing system `-dev` packages** (alsa, xkbcommon, x11, pulse, fontconfig, pipewire, dbus, way… 3. **Missing libclang for `bindgen`** — downloaded `libclang-18-dev`, `libclang1-18`, `libclang-com… 4. **Missing `lld-18`** — downloaded and added to `PATH` 5. **Broken `.so` symlinks** — copied runtime `.so` files from `/usr/lib` into the extracted lib di… The final binary at `target/release/hummingbird` starts, prints version `0.4.0-dev (1583594)`, hand…
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 30 minutes.
- Recovered from all 5 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.
- Measured 2 times, so the result is not a one-off.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.11 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.52 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hummingbird)Questions
- Does hummingbird run?
- Yes. hummingbird runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test hummingbird?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 15835949458d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test hummingbird?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hummingbird take to install?
- 30 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 hummingbird need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hummingbird?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for hummingbird?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.