transcribe-anything
Multi-backend whisper app. Blazing fast. Mac-arm optimized. Easy install. Input a local file or url and this service will transcribe it using Whisper AI. Completely private and Free 🤯🤯🤯
Runssource: GitHubhomepagePythonMITcommit c4a1808e6acf
Python, MIT licensed. The project labels itself: cli, diarization, python, speech to text, subtitles, transcription and whisper.
transcribe-anything runs. An Argusic agent installed it in 19 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
transcribe-anything 4.1.2 installed in a uv-managed Python 3.11 venv with Python 3.10 available for iso-envs; 265/278 tests pass, CLI help works, all backends ready for first-use env creation.
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.
- uv (the project's package manager) not found on PATH1 minute
- whisper iso-env requires Python 3.10 (requires-python = "==3.10.*") but only 3.11+ was available1 minute
- Install time
- 19 minutes
- Cold machine to finish
- 21 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- pytest exited 0, 265 passed, 13 skipped, 0 failed (278 collected); transcribe-anything --help printed usage and exited 0
- Model tokens used
- 59,735
- Exact commit tested
- c4a1808e6acf
- 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.
Requires --remote pointing at a daemon with --allow-
stream. Example: arecord -f S16_LE -c 1 -r 16000 -t
raw - | transcribe-anything --remote
ws://127.0.0.1:8765 --stream-in
Alright, I have everything I need. Here's the final report.
2026-10-08T02:21:43.386076Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
2026-10-08T02:21:43.386836Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
2026-10-08T02:21:43.386860Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
2026-10-08T02:21:43.386868Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
tokens used
59,735
Alright, I have everything I need. Here's the final report.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 2 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 19 minutes to install, slower than the median of the 71 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 72 cli projects Argusic has installed and timed, transcribe-anything was the 65th fastest to reach a running state, and 66 of 72 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)
clidiarizationpythonspeech-to-textsubtitlestranscriptionwhisper
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/transcribe-anything)Questions
- Does transcribe-anything run?
- Yes. transcribe-anything runs. Argusic installed and launched it on a clean machine in 19 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test transcribe-anything?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c4a1808e6acf. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test transcribe-anything?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does transcribe-anything take to install?
- 19 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 transcribe-anything need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing transcribe-anything?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does transcribe-anything compare with the alternatives?
- Of the 72 cli projects Argusic has installed and timed, transcribe-anything was the 65th fastest to reach a running state, and 66 of 72 reached one at all.
- Where is the evidence for transcribe-anything?
- 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.