What they did
u/parkskier426 has run Claude Code by voice for a few months, with local Whisper for speech to text and local Piper for speech back, wrapped in a skill that detects when they stop talking. They then added a chief agent: they talk only to it, and it hands each task to another Claude Code session running in Orca with a written spec. The chief never writes code itself. It tracks what each worker is doing, announces finished work out loud, asks for decisions and waits, and parks unanswered questions on a list. Standing rules they say once, such as not pushing to an already approved merge request, go into its rules and every worker's spec. Stream Deck buttons handle push to talk and muting.
How it went
The poster rarely touches the keyboard in a session and says that with five or more tasks running they no longer bounce between tabs answering agents, which they found draining with ADHD. When muted for meetings it falls back to notifications and typed prompts. They give no numbers on throughput.
Worth knowing
Several commenters run similar setups. One suggested an interrupt word with the mic always on. Another warned to have the chief pass on how a worker tested, not just that it finished, after a session reported a fix that was really a scripted bot with a debug hook.