zapfast
ZapFast: a fast, native WhatsApp client in Rust and egui
Runssource: GitHubhomepageRustMITcommit 4497f08cee36
Rust, MIT licensed. The project labels itself: chat, desktop app, egui, linux, macos, messaging, rust and whatsapp.
zapfast runs. An Argusic agent installed it in 74 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
ZapFast 0.21.1 builds from source, runs in demo mode, passes its full 2567-test suite, and renders both single screenshots and multi-frame headless tours.
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 96 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.
- libpipewire-0.3-dev and libspa-0.2-dev not installed (no root), so pkg-config could not find libpipewire-0.310 minutes
- libclang shared library missing for bindgen in libspa-sys build script8 minutes
- ALSA pkg-config file missing and linker could not find -lasound4 minutes
- clang stdbool.h not found -- bindgen failed on pipewire version.h3 minutes
- Install time
- 74 minutes
- Cold machine to finish
- 75 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- cargo test --features demo: 2567 passed, 0 failed; ./target/debug/zapfast --demo --demo-shot wrote 1280x800 PNG; --demo-tour --demo-tour-frames rendered 769 frames
- Model tokens used
- 894,840
- Exact commit tested
- 4497f08cee36
- 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.
- Fix: Downloaded dev packages and extracted .pc files and headers to `/home/runner/.local/`, updat… **2. libclang missing (bindgen needs it for libspa-sys)** - Fix: Downloaded `libclang-18-dev`, `libclang1-18`, and `libllvm18` packages from Ubuntu repos, ex… **3. Clang stdbool.h not found (bindgen header resolution)** - Fix: Downloaded `libclang-common-18-dev` and copied clang resource headers (including `stdbool.h`… **4. ALSA pkg-config and linker failure** - Fix: Downloaded `libasound2-dev`, copied headers and .pc file, created `libasound.so` symlink in … ## Final verification - **cargo build --features demo** succeeded (clean build: 23m 40s) - **cargo test --features demo**: 2567 passed, 0 failed, 15 ignored - **Demo app launch**: `./target/debug/zapfast --demo --demo-shot /tmp/zapfast-demo.png --demo-size… - **Tour frame capture**: `--demo-tour --demo-tour-frames ... --demo-tour-script launch` rendered 7…
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 74 minutes.
- 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 MIT, 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.
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 | 2/3 | Runs with mocks | 92.00 | 0.28 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.36 |
Topics (from GitHub)
chatdesktop-appeguilinuxmacosmessagingrustwhatsappwhatsapp-clientwindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/zapfast)Questions
- Does zapfast run?
- Yes. zapfast runs. Argusic installed and launched it on a clean machine in 74 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test zapfast?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4497f08cee36. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test zapfast?
- The run that produced this verdict cost $0.36: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does zapfast take to install?
- 74 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 zapfast need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing zapfast?
- 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.
- Where is the evidence for zapfast?
- 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.