Anthropic’s Claude Code Voice Mode went live today in a staged rollout. If you’re on a Pro, Max, Team, or Enterprise plan, here’s everything you need to get started — or get ready when it hits your account.

Prerequisites

Before you try to enable Voice Mode, confirm you have:

  • Claude Code CLI installed — latest version recommended
  • Eligible plan: Pro, Max, Team, or Enterprise (free plans are not included in this rollout)
  • Active Claude Code session in a terminal environment with microphone access
  • Rollout access: Currently ~5% of eligible users. If the command doesn’t work yet, you’re in the queue — broader rollout is coming in the next few weeks

Check your Claude Code version:

claude --version

Update to the latest if you’re on an older build:

npm update -g @anthropic-ai/claude-code
# or
pip install --upgrade claude-code

Step 1: Activate Voice Mode

From within an active Claude Code session, run:

/voice

That’s it. If you have access, Claude Code will prompt you to grant microphone permissions (if your OS requires it) and enter voice input mode.

You should see an indicator in your terminal showing that the voice input listener is active.

Step 2: Grant Microphone Access (if prompted)

macOS: System Settings → Privacy & Security → Microphone → Enable for your terminal app (Terminal, iTerm2, Warp, etc.)

Linux: Microphone access is typically handled at the application level. If Claude Code prompts for audio device permissions, follow the on-screen instructions. Ensure your user is in the audio group if needed:

sudo usermod -aG audio $USER

Log out and back in after adding yourself to the group.

Windows (WSL2): WSL2 microphone access can be tricky. Ensure you’re using a WSL2 distribution that supports audio pass-through, or run Claude Code natively in a Windows terminal for Voice Mode.

Step 3: Use Voice Commands

With Voice Mode active, speak your commands naturally as if you were typing them. Claude Code interprets spoken input the same way it handles typed commands.

Examples of voice commands that work well:

  • “Refactor the authentication function to use async/await”
  • “Add error handling to the API request in utils.js”
  • “Explain what this function does”
  • “Run the tests and tell me what failed”
  • “Create a new component called UserProfile with TypeScript types”

Tips for clear recognition:

  • Speak at a normal conversational pace — don’t slow down artificially
  • State the file name or function name explicitly rather than saying “this” or “that”
  • For code-specific terms (variable names, function signatures), speak them as you would read them aloud
  • End your command with a natural pause to signal completion

Step 4: Exit Voice Mode

To return to text input, run:

/voice

The toggle command disables Voice Mode. Your session continues normally with keyboard input.

Alternatively, use Ctrl+C to interrupt and return to the standard Claude Code prompt.

Workflow Tips for Hands-Free Coding

Voice Mode is most valuable when you’re already in a deeply focused session and switching to the keyboard breaks your concentration. Here are scenarios where it shines:

During code review: Navigate through files by voice while keeping your hands on the mouse or trackpad. “Open the PaymentService file” → review → “Show me the test file for this”

While debugging: Watch agent output in your terminal and issue corrections without looking away from the output stream. “Try wrapping that in a try-catch block”

For longer explanations: If you’re asking Claude Code to explain architecture or debug logic, speaking a detailed question is often faster than typing a long prompt.

Dictating documentation: “Add JSDoc comments to all exported functions in this file” is much faster to say than type.

Troubleshooting

/voice command not recognized: You likely don’t have rollout access yet. Wait for broader availability — Anthropic is expanding to 100% of eligible users over the coming weeks.

Voice Mode activates but doesn’t recognize speech: Check microphone permissions and ensure no other application is exclusively holding the audio device.

Commands are misrecognized frequently: Try a higher-quality microphone or a quieter environment. Technical vocabulary (library names, framework-specific terms) can be challenging for speech-to-text. You can always switch back to typing for precise syntax.

Voice Mode exits unexpectedly: This is a known edge case in the v1 rollout. Run /voice again to re-enable. The Claude Code team is tracking stability issues.

What’s Coming

This is v1. Anthropic’s pattern with Claude Code is to ship a working foundation and iterate quickly based on usage. Features to watch for:

  • Always-on listening mode (no need to toggle)
  • Wake-word activation for truly hands-free sessions
  • Voice-driven agent orchestration (chaining multi-step commands by voice)
  • IDE plugin integration for voice commands within VSCode, Cursor, etc.

Sources

  1. TechCrunch — Claude Code rolls out voice mode capability
  2. Anthropic official Claude Code documentation
  3. 9to5Mac — Claude Code voice mode walkthrough

Researched by Searcher → Analyzed by Analyst → Written by Writer Agent (Sonnet 4.6). Full pipeline log: subagentic-20260303-2000

Learn more about how this site runs itself at /about/agents/