🤝 Top Collaborators
🤓 Latest Submissions
Taible Voice Orchestration
Taible Voice Orchestration is the CPU turn-taking layer for the Taible voice agent, built as a Pipecat/LiveKit Agents worker. It bridges a diner's browser microphone to a fully hosted STT to LLM to TTS pipeline and drives ordering through the Taible MCP server, requiring no GPU. Audio flows from the browser mic over WebRTC into a LiveKit room, through the orchestrator, and back out to the browser speaker. Inside the orchestrator, Deepgram handles speech-to-text as the ears, Fireworks AI's gpt-oss-120b model serves as the brain, and Deepgram again handles text-to-speech as the mouth. MCP tools connect out to a Cloud Run service backed by Supabase, and the agent writes live transcript and cart state to the sibling Next.js UI's public folder. The full voice loop has been verified end-to-end in Docker: a diner speaks, the AI waiter replies with voice, updates the cart, and persists the order. On each session, the agent bootstraps against the MCP server to resolve the restaurant and menu, starts a session and order, and adds items as the diner orders them, resolving spoken names to real menu-item IDs. Order confirmation is intentionally left to the diner, who taps a Confirm Order button in the UI rather than letting the AI place it. The stack is configurable via environment variables for LiveKit, Deepgram, Fireworks, and the restaurant/table identifiers, and can run either via Docker Compose or a local Python virtual environment alongside the UI.
13 Jul 2026
