pickfit

BrowseLocal AI tools

wavo

Local GPU speech-to-text CLI and Rust library for Parakeet, GigaAM and Whisper models.

Tested on Linux

Use it

Linux x86_64

  1. Download dev binary and install to ~/.local/bin

    mkdir -p ~/.local/bin && curl -fL -o /tmp/wavo-dev.tar.gz https://github.com/vladkens/wavo/releases/download/dev/wavo-dev-x86_64-unknown-linux-gnu.tar.gz && tar -xzf /tmp/wavo-dev.tar.gz -C /tmp && cp /tmp/wavo ~/.local/bin/wavo && chmod +x ~/.local/bin/wavo
Where the README and reality differ
  • README: download the binary from the latest release
    What worked: use dev-release binary (v0.3.1-23-ga3b5c3b) which has list/debug/serve and parakeet-ultra; latest release v0.3.1 binary has no wavo debug or wavo serve

Check that it works

wavo --version

The output should contain “wavo 0.3.1-23-ga3b5c3b”.

First thing to try

wavo list

Run wavo list first to see the available speech models.

What it does

  • Transcribe speech to text on your own computer
    Not tested
  • Save transcripts as SRT subtitle files
    Not tested
  • Run a local transcription API server
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 3 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • transcribe an audio file to text
  • generate SRT subtitles from audio
  • serve OpenAI-compatible local transcription API

An alternative to transcribe.cpp, whisper.cpp and sherpa-onnx.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 0.3.1-23-ga3b5c3b

Differences the test machine hit

  • README: cargo install wavo
    In the test: download dev-release tarball wavo-dev-x86_64-unknown-linux-gnu.tar.gz and copy wavo to ~/.local/bin (cargo needs a Rust toolchain the box must not install)

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.