Authorization notice. Speech CPP is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Remote script. The install step runs a script fetched from the internet, so review it before running.
Who it is forA developer building a web app or script that already calls OpenAI's audio API and wants to keep audio processing on their own computer.
The problemAudio requests to a hosted API send private audio off the machine and add per-call costs during development.
The outcomeSpeech and transcription requests answered by a local server through the same API shape, using a changed base URL.
What you need first
- macOS on Apple silicon, Linux on x86-64, or Windows x64
- Internet access to fetch the installer and models from Hugging Face the first time
- Free disk space for the model files, for example 1.21 GB for qwen3-tts-0.6b
- A terminal (PowerShell on Windows)
- A microphone, for live transcription
Steps
- Install speech using the installer for your platform.
- Run
speech serve qwen3-tts-0.6b qwen3-asr-0.6bto start the server. - Send a speech request with
curl http://127.0.0.1:8080/v1/audio/speech -H 'Content-Type: application/json' -d '{"input": "Hello.", "voice": "ryan"}' -o hello.wav. (inferred, check the README) - Send a transcription with
curl http://127.0.0.1:8080/v1/audio/transcriptions -F [email protected].
Prompt for your agent
In the nyosegawa/speech.cpp repo, install speech, run `speech serve qwen3-tts-0.6b qwen3-asr-0.6b`, and then call the local POST /v1/audio/transcriptions endpoint on 127.0.0.1:8080 with a WAVE file at <path>. Expected output: a JSON or text transcript of the file. Verify that the text matches the audio.
Caveat. The server listens on 127.0.0.1 and has no authentication, so do not expose it on a shared or public network.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page