Introduction

claudio is a voice in front of your coding-agent sessions: you talk to them instead of typing. Ask a question and it answers in a few short sentences. Ask for work and it hands the task to one of your sessions, then tells you when that session is done, needs a permission, or asks you to choose.

It doesn't read your sessions' screens aloud. A separate brain listens to you, decides whether you're discussing or asking for work, and narrates what your sessions report back in plain words.

How the parts fit togetherCopy Anchor Link

claudio has three parts of its own, and it works with the sessions you already run:

• Ears: Deepgram Flux turns your speech into text as you talk and decides when your turn has ended
• Brain: one long-lived claude process, driven through the Claude Agent SDK, with a short persona. It answers questions itself and hands work to a session, never doing the work itself
• Mouth: Deepgram Aura or ElevenLabs speaks the brain's reply one sentence at a time
• Your sessions: the coding-agent sessions claudio hands work to. They report back through three Claude Code hooks. Where they live, and where you see claudio, are the platforms you pick

One session is the orchestrator: the one that gets your tasks unless you name another. Passing a task to a session is a handoff.

What you needCopy Anchor Link

• A Deepgram API key, for the ears and the default mouth
• Claude Code, signed in: the brain runs through your Claude Code login
• macOS, since the echo canceller is Apple's voice-processing unit
• Python 3.11 or later and uv
• Optional: the Xcode command line tools, so you can talk over claudio on speakers instead of headphones

And one of these, for your sessions:

• bb, whose threads are the sessions; its claudio panel is optional. See bb
• cmux, whose panes are the sessions. See cmux