Say the whole task to Claude Code.
Claude Code's built-in /voice: start there if it fits
Claude Code has its own dictation. According to its documentation, you run /voice, then hold Space to talk (hold mode) or use /voice tap to tap once to start and again to send. In tap mode, Claude Code submits the prompt when the transcript is at least three words long. Transcription is tuned for coding vocabulary, and the VS Code extension supports it too.
If you sign in with a Claude.ai account and only dictate to Claude Code, try /voice first.
When a separate dictation app makes sense
- You don't sign in with Claude.ai. Claude Code's docs say /voice is not available when it uses an Anthropic API key directly, Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry. Whispek doesn't depend on how Claude Code is signed in: it only produces text.
- You work over SSH or in a cloud session. The docs say /voice needs a local microphone and does not work in cloud or SSH sessions, or in VS Code Remote sessions. With Whispek you dictate on your own computer, then copy and paste the reviewed text into the remote session.
- You want to read the prompt before it is sent. With Whispek nothing is sent until you press Enter in Claude Code.
- Claude Code is one of several places you write. The same Whispek shortcut works in Cursor, browser AI chats, GitHub, Slack and email.
Claude Code /voice vs Whispek
| Claude Code /voice | Whispek | |
|---|---|---|
| Where it works | The Claude Code CLI and VS Code extension, per Anthropic's docs | Compatible text fields across your desktop and browser; for a terminal, dictate into a notes field or chat box, then copy and paste |
| Sign-in | Claude.ai account required, per the docs | Whispek account; independent of how Claude Code is signed in |
| Remote and SSH sessions | Not available, per the docs | Dictate locally, then copy and paste into the session |
| Sending | Hold mode waits for Enter by default; tap mode submits at three or more words | You copy and paste the text and press Enter yourself |
| Vocabulary | Tuned for coding terms; adds your project and git branch names as hints, per the docs | Dictionary for repository, library and service names |
| Rewrite and reuse | Not described in the docs | Transforms (Create an AI prompt or your own instructions), Snippets, History |
| Price | Included with Claude Code; does not use Claude messages or tokens, per the docs | Free every 7 days; Pro $12/mo, or $8.25/mo billed $99 yearly. Unlimited. |
How to dictate a Claude Code prompt with Whispek
- Open somewhere to draft. A notes window, a chat box or your editor's scratch file. Say the context, goal, constraints and done-when check. This works the same for the Claude Code VS Code extension: draft first, then copy and paste into its input box.
- Press your Voice input shortcut and describe the task. Right Alt on Windows, Right Option on macOS, Left Ctrl + Left Alt + Space on Linux; you can change the Voice input shortcut on the Home screen. Turn on Settings > Voice & translation > Live transcription display to see the transcript above the capsule while you talk.
- Rambled? Select the text, open the Transforms window and choose Create an AI prompt: you get a clean, structured prompt in one step. For your words as spoken, choose Original in Style > Cleanup before dictating.
- Copy and paste it into Claude Code, add exact context, then send. Add files with @ in Claude Code, paste exact errors and paths, read the prompt once and press Enter. If the text did not appear where you expected, copy it from History.
A spoken structure for a Claude Code task
Say it in this order. You don't need the labels, but they keep you from skipping a part.
- Goal: "Make the retry logic in the payment webhook handler idempotent."
- Context: "Duplicate events sometimes create two refunds. The handler is in the webhooks folder."
- Constraints: "Don't change the public API or the database schema. No new dependencies."
- Done when: "Add a test that sends the same event twice. The existing tests still pass."
- Plan first: "Explain the cause and the files you will change before editing."
Paste the stack trace and the exact handler path yourself rather than reading them out.
Using Codex CLI too?
The same approach works for Codex CLI. Codex CLI's /voice is a spoken conversation with Codex, and in October 2026 an OpenAI maintainer said there are no plans for one-way dictation in the CLI. Dictate into a notes field or chat box, review, then copy and paste into the Codex prompt.
Keep names right and reuse what works
- Dictionary: add Kubernetes, PostgreSQL, Tauri, useEffect and pnpm once, and they're in your dictionary on every computer you sign in to, so Whispek writes them your way. Bring in a whole list with More actions > Import terms.
- Snippets: save standing instructions, such as "Explain the plan before editing and don't touch the migrations."
- History: find a prompt that worked last week and copy it into a new session.
- New transform: open Transforms, choose New transform and write Instructions such as "Rewrite as a coding task with Goal, Context, Constraints and Done when. Keep file names, numbers and negations exactly as spoken."
What Whispek does not do in Claude Code
- It does not type commands for you to run. Don't dictate shell commands to run directly; describe the goal and review what Claude Code proposes.
- It does not read your repository, tag files or connect to your Claude account.
- It does not send prompts. You review the text and press Enter.
- It needs internet. Speech is processed in the cloud, so check your team's rules before dictating private code details.
Pricing
Whispek is free every 7 days. Pro is unlimited for $8.25/month, billed yearly ($99), or $12 month to month. Prices exclude tax.
Your next Claude Code task, out loud
Install Whispek, open a notes window next to your terminal and say the task you would normally cut down to one line.