How to Dictate in Claude Code (and What /voice Doesn't Cover)

Claude Code quietly turned the terminal into the place you write the most prose all day. Task briefs, plan-mode feedback, review instructions — an agentic session is paragraphs of intent, and typing those paragraphs is now the slowest part of the loop. Developers average roughly 40 words per minute typing; natural speech runs 150 or more.

TL;DR: There are two ways to dictate in Claude Code. The built-in way: type /voice in a session, hold the spacebar, talk, release — the transcript drops into your prompt. The system-wide way: run a dictation tool like Voibe that types wherever your cursor is — the Claude Code prompt, the shell itself, your editor, a second agent pane, the browser, Slack. /voice is the zero-setup option; the system-wide tool is the one that covers your whole workflow on Mac and Windows, and it can keep the audio on your machine. This guide sets up both.

An agentic coding session involves far more prose than the prompt box. In a typical hour with Claude Code you write: the task brief, answers to clarifying questions, plan-mode approvals and corrections, mid-session steering ("stop — check the migration first"), commit message tweaks, a PR description in the browser, and a Slack update about what shipped. Claude Code's /voice covers exactly one of those surfaces: the prompt input.

That's the honest framing for the rest of this guide: /voice is genuinely good at the surface it targets, and a system-wide tool is how voice covers the workflow around it. Most heavy voice users end up running both.

Claude Code's voice mode shipped on March 3, 2026 (TechCrunch) and has since expanded broadly. It is included at no extra cost on Pro, Max, Team, and Enterprise plans, and it is a terminal-only interactive feature — push-to-talk, no always-listening mode, English-focused in the initial rollout. Per the official voice dictation docs, setup takes under a minute:

1. Update Claude Code. Run claude update so you're on a build with voice support.
2. Type /voice in an active session. This enables voice mode for the session.
3. Hold the spacebar and talk. Release to transcribe. The transcript is inserted at your cursor in the prompt input — after anything you've already typed.
4. Edit, then submit. The transcript is ordinary prompt text. Fix a word, add a file path by keyboard, keep talking — voice inserts into your input rather than replacing it.

Two details worth knowing. First, reported testing indicates transcription tokens don't count against your rate limits — you pay (in usage) when you submit the prompt, as with typing. Second, if /voice isn't available in your session, update first; the feature reached users gradually through 2026, and it requires a paid plan.

A system-wide tool inserts text wherever your cursor is, exactly like a keystroke — which is what makes it cover the shell, your editor, the browser, and every agent pane, not just the Claude Code prompt. This guide uses Voibe — ours, and the one built for exactly this workflow — but the steps apply in spirit to any tool covered at the end.

1. Install. On Mac, download the .dmg and drag it to Applications; on Apple Silicon (M1–M4, macOS 13+) it downloads a local Whisper model on first run. On Windows, grab the installer from getvoibe.com. No account needed, 7-day free trial.
2. Grant permissions. On macOS: Accessibility (System Settings > Privacy & Security > Accessibility — this is what lets it type into your terminal) and Microphone. On Windows, allow microphone access when prompted.
3. Set a hold-to-talk hotkey. Voibe defaults to holding Fn on Mac: press, speak, release, and the text lands at your cursor. Pick a key you can hold while your hands stay on the keyboard — see our Mac dictation keyboard shortcuts guide for conflict-free options.
4. Load your Dictionary. Add the terms Claude Code sessions are full of — worktree, monorepo, Tailwind, pnpm, Vitest, your project and service names — so they transcribe correctly every time. This is a real dictionary that influences transcription, not a find-and-replace table.
5. Bonus for editor terminals: if you run Claude Code inside VS Code or Cursor's integrated terminal, enable Developer Mode — Voibe detects the open workspace and resolves spoken file and folder names to their exact spelling, so "update user service" lands as userService.ts. See how to dictate in Cursor for that setup.

On Windows: Voibe runs on Mac and Windows. The Windows app (launched July 2026) is a ground-up native app — not an Electron port — that transcribes through Voibe's private zero-retention cloud; the fully on-device mode is Mac-only (Apple Silicon). The free baseline on Windows is voice typing with Win+H, covered in our Windows dictation guide — it works in terminals but has no custom vocabulary, so CLI terms come out mangled.

The strongest case for the system-wide approach shows up the moment you run more than one agent. Multi-agent setups are becoming normal: several Claude Code sessions across git worktrees, or a dedicated multiplexer like cmux — an open-source native macOS terminal, built on the GPU-accelerated Ghostty, designed specifically for running AI coding agents in parallel workspaces.

/voice is a per-session feature: it types into the one Claude Code prompt it was enabled in. A system-wide hotkey doesn't care which pane is focused or which agent runs inside it. Click into workspace two, hold the key, redirect that agent; click into workspace three — same key — approve a plan. It works identically whether the pane is running Claude Code, Gemini CLI, or Codex, because the tool types wherever your cursor is.

Steering three agents by keyboard means re-typing context all day. Steering them by voice is one held key and a sentence per pane. For the terminal-side setup in iTerm2, Warp, and Ghostty — including the Secure Keyboard Entry trap — see our companion guide, how to dictate in your terminal, and for where dictation fits in a full agentic stack, our agentic engineering tools piece.

Dictating to an agent rewards a different style than dictating an email. What works, from daily use:

• Task brief: "Add rate limiting to the public API routes. Use the existing Redis client, keep the limits configurable per route, and write tests before you refactor anything." — goal, constraints, guardrails, in one breath.
• Plan-mode feedback: "The plan looks right except step three — don't touch the schema. Work around it with a view and flag the tradeoff in your summary."
• Mid-session steering: "Stop. The test failure is in the fixture, not the handler. Re-read the setup file before changing anything else."
• Review requests: "Diff this branch against main and list anything that changes public behavior, ordered by risk."

Speak in short, structured chunks — a focused two-sentence instruction transcribes far better than a 60-word run-on. For a repeatable structure (Goal, Inputs, Constraints, Example, Output), use the Five-Part Voice Prompt framework from our guide to voice-prompting ChatGPT, Claude, and Cursor. And always glance at the transcript before you hit Enter: with /voice and system-wide tools alike, the text is editable input, not a fired command.

Voice adds one more data path to think about. Anthropic has not published whether /voice transcription runs locally or on its servers; Claude Code is a cloud-connected tool, so the practical rule is to treat spoken input like everything else in your session — governed by your plan's data and training settings. Our Claude Code safety guide breaks those down by tier, and the privacy settings guide covers the training opt-out and network toggles worth two minutes of your time.

A system-wide on-device tool changes the audio side of that equation. Voibe's on-device mode transcribes on your Mac's Apple Silicon — the recording never leaves the machine, and only the finished text you submit enters the Claude Code session. Spoken prompts routinely contain file names, architecture details, and unreleased product plans; on-device transcription keeps that audio inside your security perimeter. On Windows and Intel Macs, Voibe uses its private zero-retention cloud: audio is never stored, sold, or used to train AI. For the deeper comparison, see cloud vs local dictation.

One related prompt worth recognizing before you answer it on autopilot: Claude Code's post-rating question about sharing your session transcript. Answering yes ships the whole session — our session transcript privacy guide explains exactly what uploads.

/voice isn't available in my session

Run claude update first — voice mode reached users gradually through 2026, and older builds don't have it. It also requires a Pro, Max, Team, or Enterprise plan. If the command is still unrecognized after updating, check the voice dictation docs for current availability.

Dictated text isn't appearing in the terminal

For system-wide tools this is almost always one of two things. On macOS, confirm the Accessibility permission (System Settings > Privacy & Security > Accessibility); if it's enabled and still not typing, remove and re-add the app to reset the grant. The sneakier cause is Secure Keyboard Entry: iTerm2 and Apple's Terminal both have it, and while it's on, macOS blocks accessibility tools and global hotkeys — dictation silently stops working in that window. Toggle it off from the app menu (e.g. iTerm2 > Secure Keyboard Entry; see the iTerm2 FAQ).

Technical terms come out wrong

General speech models don't know your stack. Add library names, CLI tools, and project terms to your dictation app's custom Dictionary — once added, they transcribe correctly every time. Claude Code's /voice has no user-editable vocabulary, so a mangled term there means editing the prompt by hand before submitting.

The microphone isn't picking up

Check that your dictation app (not the terminal) has microphone permission, and that the right input device is selected — a common failure after plugging in a USB mic or switching to AirPods. The terminal never needs mic access; the dictation app captures audio and delivers text.

Four practical options, with the trade-off that matters for each:

• Voibe — system-wide on Mac and Windows, with a real custom Dictionary and Developer Mode for editor terminals. On Apple Silicon it runs fully on-device; on Windows and Intel Macs it uses a private zero-retention cloud. $149 lifetime or $7.50/month, 7-day free trial, no account. The fit for daily agent work: one hotkey across Claude Code, the shell, cmux panes, and everything else. See our best dictation software for developers roundup.
• Claude Code /voice — built in, free with your plan, zero setup. Prompt-only, push-to-talk via spacebar, English-focused, no custom vocabulary. The right answer for trying voice today.
• Superwhisper — on-device Whisper modes, and v2.13 added a dedicated Claude Code / OpenCode terminal-agent integration. Deeply configurable (its per-app modes are the signature), with a setup-complexity trade-off users consistently flag. ~$8.49/month or $249.99 lifetime — $100 more than Voibe's $149 lifetime.
• Wispr Flow — polished cloud dictation across Mac and Windows, $144/year with no lifetime option. Capable, but transcription runs in the cloud — weigh that against dictating unreleased code and architecture out loud.
• Apple Dictation / Windows voice typing (Win+H) — the free built-ins. Fine for a quick sentence; both lack custom vocabulary, so CLI and project terms need hand-fixing.

Basics

Does Claude Code have voice input?
Yes — type /voice in a session, hold spacebar to talk, release to transcribe. It rolled out from March 2026 on Pro, Max, Team, and Enterprise plans. Any system-wide dictation tool also types into the Claude Code prompt, plus every other app.

Is /voice the same as Claude's voice conversations on mobile?
No. Claude Code's /voice is dictation — speech becomes editable text in your prompt. The Claude app's voice feature is a spoken conversation. In Claude Code you keep full control of what gets submitted.

Setup

Can I dictate into Claude Code on Windows?
Yes — /voice inside the prompt, or a system-wide tool for every surface. Voibe for Windows is a native app using a private zero-retention cloud; Win+H voice typing is the free baseline.

Which hotkey should I use for a system-wide tool?
One you can hold comfortably while your hands stay on the keyboard — Voibe defaults to Fn on Mac. Avoid keys your terminal multiplexer already binds.

Privacy

Is dictating proprietary code safe?
Spoken prompts contain file names, architecture, and plans. With on-device transcription the audio never leaves your machine — only the text you choose to submit enters the session. With cloud transcription (including /voice, whose processing location is undocumented), treat audio like the rest of your session data.

Workflow

Does /voice use up my rate limits?
Reported testing says transcription itself doesn't count; usage is consumed when you submit the prompt, same as typing.

Can one dictation setup drive multiple agents?
Yes — that's the system-wide tool's strongest case. One hold-to-talk hotkey types into whichever pane is focused: several Claude Code sessions, cmux workspaces, or other agent CLIs.

The prose is the bottleneck now. Claude Code's /voice makes the prompt speakable today — type it in your next session and you're dictating in under a minute. When you notice how much of your day is still typed — the shell, the second agent pane, the PR description, the Slack update — that's the moment for a system-wide tool.

Voibe is built for that layer: on-device on Apple Silicon, native on Windows via a private zero-retention cloud, one hotkey everywhere. Download it free (7-day trial, no account) and dictate your next task brief instead of typing it.

Keep going:

• How to dictate in your terminal — iTerm2, Warp, Ghostty, and the Secure Keyboard Entry trap
• How to voice-prompt ChatGPT, Claude, and Cursor — the Five-Part Voice Prompt framework
• How to dictate in Cursor — Developer Mode and the AI editor
• Is Claude Code safe? — privacy and data retention by tier
• Best dictation software for developers — the full buyer's view
• Getting started with Voibe — complete setup guide