VOICE · 4 MIN READ

When speaking helps you code

Use voice to capture intent and feedback quickly while keeping command execution under your control.

Speak the idea, then inspect the text

Voice is useful when the thought is larger than the sentence you want to type. Explain a bug while looking at the screen. Describe the expected behavior. Dictate a review comment after reading a diff. These are all natural speech tasks.

Code and terminal input need one extra step. Recognition can mishear a flag, filename, or symbol. A safe voice workflow inserts the transcript as editable text and waits for you to submit it. That keeps dictation fast without turning recognition errors into executed commands.

Keep the recording state obvious

A shortcut should tell you whether recording started, whether it is processing, and where the text will land. If speech recognition fails or permission is denied, the app should say so in place. A recorder that simply disappears leaves you guessing about the microphone, the shortcut, and your words.

A compact floating control can help when you are in another app, but it should not cover the thing you are reading. Clear state and predictable placement matter more than a large animation.

Pick the right destination

A transcript meant for a coding terminal belongs in that terminal draft. A transcript meant for an agent conversation belongs in the chat composer. Changing modes after recording can be surprising, so choose the destination before you speak and show it while recording.

Voice works best as another input method for an existing workflow. You should be able to edit, discard, or submit the words exactly as you would with a keyboard.