Lately I’ve been using voice input for prompting AI more and more. Before this, I was very much a keyboard person — I thought the keyboard was cool. I can type fast, I work in Emacs with all its commands and shortcuts for navigating around text, and that always felt very efficient. But I’m seeing more and more power users and senior developers using voice input in their day-to-day development work. I even came across a meme post about how developers of the future will only need two buttons and a pedal for prompting AI. So one day, I decided to try it for myself. Claude Code has a built-in voice mode, so I just tried it — and it actually feels much better.
One major issue I had before was with the Claude Opus 5 model producing very lengthy output. The response overflows past one screen, so you end up scrolling down and down to keep reading while trying to hold on to your thoughts — by the time you reach the end, you’re juggling reading and note-taking at the same time. Voice input changed exactly that flow: instead of pausing to type, you press the voice shortcut, say out loud your thoughts or suggestions about what you just read, release the voice key, and keep scrolling. Reading and responding become one continuous loop instead of two competing activities.
It just feels more natural — more like actually communicating with the agent. Sometimes you almost wish the agent could talk back to you, like talking to an actual person. But voice input makes providing prompts much easier and reduces the mental load and pressure of writing.
There’s also the simple input-speed comparison: how many words you can type per minute versus how many you can say per minute. With voice, you simply get more prompt out. And with AI, providing a richer prompt means it does more of exactly what you want.