Someone lost their voice from talking to AI all day
I built Rubber Duck, a voice coding agent. A Todoist Ramble clone for Things 3 that streams audio to Gemini Flash 2.5 Live and runs tool calls. Commandment, an open source WisprFlow alternative. Each one started from the same observation: typing is a bottleneck when the listener speaks natural language.
Based on voice AI projects built between late 2025 and early 2026.
The usage pattern that tells you something shifted
Someone in our community literally lost his voice from talking to AI. Not a metaphor. He lost his voice from talking to AI all day. That tells you something shifted.
When a tool causes physical strain, you are past novelty. That is adoption. Uncomfortable, unsustainable, but real.
Voice removes the translation layer
Voice removes the translation layer between thinking and doing. You do not figure out how to type what you mean. You say it. For tasks, code, controlling tools, the mouth is faster than the fingers when the listener is an LLM.
Typing friction is not speed. It is the cognitive overhead of translating thought into structured input. Voice skips that. Think it, say it, agent does it.
Until voice tools mature, a high performing keyboard is still the fastest physical interface between thought and shipped code.
The interface is collapsing
The tools I am building now would have been science fiction two years ago. Streaming audio to a model that runs tool calls in real time. Talking to your computer and having it do what you said.
The interface between intent and execution is collapsing. Voice collapses it fastest. The question is not whether speech replaces typing for AI. It is how fast the tooling catches up to the behaviour people already want.