voxtype
Voice-to-text with push-to-talk for Wayland compositors
Runssource: GitHubRustMITcommit 9c35b72b4fa3
Rust, MIT licensed. The project labels itself: accessibility, dictation, gnome, hyprland, kde, linux, offline and push to talk.
voxtype runs. An Argusic agent installed it in 23 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Voxtype v1.1.0 builds and passes its full test suite (1159 passed, 0 failed) on Ubuntu 24.04 amd64 with Rust 1.99.0, after manually providing alsa and clang/LLVM development libraries extracted from apt packages without root privileges. The CLI binary responds correctly to --version and --help.
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.
- bindgen fails: cannot open libclang shared library (libLLVM.so.18.1 missing)7 minutes
- alsa-sys build fails: pkg-config cannot find alsa.pc5 minutes
- linker: unable to find -lasound2 minutes
- rustc/cargo not found1 minute
- Install time
- 23 minutes
- Cold machine to finish
- 27 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- cargo test: 1159 passed, 0 failed, 2 ignored; voxtype --version --help both returned expected output; binary built at /work/repo/target/release/voxtype
- Model tokens used
- 106,901
- Exact commit tested
- 9c35b72b4fa3
- 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.
exec /bin/sh -lc 'date +%s' in /work/repo succeeded in 0ms: 1791315785 exec /bin/sh -lc 'echo "Start timestamp estimate: session began around 19:20 UTC = $((1791315785 - 25*60… succeeded in 0ms: Start timestamp estimate: session began around 19:20 UTC = 1791314285 Here's the final assessment: tokens used 106,901 Here's the final assessment:
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 MIT, as reported by its host.
What did not, or is not known
- Took 23 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 accessibility projects Argusic has installed and timed, voxtype was the 3rd 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.
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
Topics (from GitHub)
accessibilitydictationgnomehyprlandkdelinuxofflinepush-to-talkrustspeech-recognitionspeech-to-textswayvoice-to-textvoice-typingwaylandwhisperwhisper-cpp
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/voxtype)Questions
- Does voxtype run?
- Yes. voxtype runs. Argusic installed and launched it on a clean machine in 23 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test voxtype?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9c35b72b4fa3. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test voxtype?
- 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 voxtype take to install?
- 23 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 voxtype need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing voxtype?
- 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 voxtype compare with the alternatives?
- Of the 4 accessibility projects Argusic has installed and timed, voxtype was the 3rd fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for voxtype?
- 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.