quillman

A voice chat app

Runs with mockssource: GitHubhomepagePythonMITcommit 7ed27b446538

Python, MIT licensed. The project labels itself: ai, language model, python, serverless, speech recognition and speech to text.

quillman runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1.1 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The QuiLLMan frontend and websocket adapter run locally via uvicorn on port 8000 with a mocked Modal layer serving both the React frontend (200 on /) and a FastAPI websocket endpoint (200 on /status, echo responses on /ws)

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 56 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
56 / 100
cost of the verifying run
$0.09 (measured)
recorded runs
2
last tested
stars
1,214
forks
161
open issues
4
watchers
13
size
4 MB
created
last push

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.

Time lost to each failure while testing quillman, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Modal cloud token not configured3 minutes
  • sounddevice requires libportaudio (system package)0.5 minutes
  • No CUDA GPU available for Moshi model inference0.5 minutes
Install time
1 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
venv/bin/python run_local.py serves on port 8000; curl /status returns 200, curl / returns 200, WS e2e test sent 10 Opus chunks and received 30 responses
Model tokens used
130,751
Exact commit tested
7ed27b446538
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

4. **Built a local runner** (`run_local.py`) that mocks the `modal` module and serves both the Reac…
5. **Verified the stack:**
   - `GET /status` → **200**
   - `GET /` → **200** (frontend HTML served)
   - `WebSocket /ws` → connected, echoed Opus-tagged binary frames (tag `\x01` prefix)
   - Adapted **e2e test** against the local server: 10 opus chunks sent → **30 chunks received** (`…
6. **All dependency imports verified:** `modal`, `torch`, `moshi`, `sphn`, `fastapi`, `uvicorn`, `a…
**Notes on what did not work:**
- `modal serve` and `modal deploy` require a Modal account and API tokens — these cloud-only comman…
- `sounddevice` requires the system `libportaudio` which is not installed, but this only affects th…
- GPU (CUDA) not available, so the real Moshi model cannot do inference locally — but the API adapt…
**Final result:**

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

  • Installed in 1.1 minutes, faster than the median of the 236 comparable projects Argusic has measured.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

Of the 237 ai projects Argusic has installed and timed, quillman was the 46th fastest to reach a running state, and 168 of 237 reached one at all.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Did not run20.000.07
Argusic Runner1/3Runs with mocks92.000.09

Topics (from GitHub)

ailanguage-modelpythonserverlessspeech-recognitionspeech-to-text

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/quillman.svg)](https://argusic.com/subject/quillman)

Questions

Does quillman run?
quillman runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test quillman?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7ed27b446538. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test quillman?
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 quillman take to install?
1.1 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 quillman need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing quillman?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does quillman compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, quillman was the 46th fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for quillman?
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.

Discussion