Credentials. The setup stores a Bailian or other provider API Key in the config file, so keep that file private and do not commit it to a repo.
Who it is forA developer who wants to keep talking through a problem while a coding Agent edits files or runs tools in the background.
The problemWaiting on a coding Agent to finish a task blocks the conversation, so the developer cannot ask follow-up questions or check progress.
The outcomeThe developer talks to the voice frontend, sends a task to the backend Agent, asks for progress, and gets the result back in the same conversation.
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
- Install the runtime with
npm install -g qwen-audio-agent. - Create your config and add your API Key with
qwenaudio config. - Set AGENT_PROTOCOL in the config to the backend Agent you want, for example openclaw, or leave it empty for frontend-only mode.
- Start the Gateway with
qwenaudioin one terminal. - Open a second terminal and start the TUI with
qwenaudio tui, then speak your task.
Prompt for your agent
Use the repo QwenAudio/qwen-audio-agent to set up a voice session that delegates <task description> to a backend coding Agent. Confirm the Gateway starts and the TUI connects, then report the task status returned in the conversation. Verify that the Gateway log shows the task was created before reporting success.
Caveat. The README says the backend Agent must be installed and configured separately, and some backends are marked as not yet fully verified.
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