DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run a voice frontend stack with local speech models with Qwen Audio Agent

Connect the Hugging Face speech-to-speech service so VAD, STT, LLM, and TTS run locally.

Who it is forA privacy-minded developer who wants voice conversation without sending audio to a cloud provider.

The problemCloud voice services send audio off the machine, which some users cannot accept for their work.

The outcomeYou run the Hugging Face speech-to-speech service locally, point the runtime at its URL, and have a voice conversation that uses local components.

What you need first

  • Node.js 22.22.2+ or 24.15.0+ and npm 10+
  • A Bailian (DashScope) API Key or another supported voice frontend key, such as an OpenAI or Google API Key
  • A backend Agent you want to use, such as Qwen Code, OpenCode, or Claude Code, installed through the one-click install option
  • Microphone access on your computer

Steps

  1. Install the runtime with npm install -g qwen-audio-agent.
  2. Start the Hugging Face Speech-to-Speech service on your machine using its own instructions.
  3. Set the voice frontend in the config to Hugging Face Speech-to-Speech and enter the service URL.
  4. Start the Gateway with qwenaudio and open the TUI with qwenaudio tui.
  5. Speak a short question and confirm the reply comes from the local service.

Prompt for your agent

Use the repo QwenAudio/qwen-audio-agent to connect the Hugging Face speech-to-speech frontend running at <service URL>. Report the frontend name shown in the Gateway and whether a spoken question gets a reply. Verify the Gateway log shows the local service URL before reporting success.

Caveat. The README says the frontend is configurable for STT, LLM, and TTS only once the service is running, and the exact service setup is in the linked voice frontend guide, so the first run depends on that separate setup.

Share: 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