claude-code - 💡(How to fix) Fix [DOCS] Voice dictation hint text hardcodes `Space` instead of the rebound push-to-talk key

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/voice-dictation

Section/Topic

Voice dictation footer hints and the “Rebind the dictation key” section

Current Documentation

The page currently says:

While voice dictation is enabled, the input footer shows a hold Space to speak hint when the prompt is empty. The hint text is the same in both modes, and it does not appear if you have a custom status line configured.

Hold Space to start recording. Claude Code detects a held key by watching for rapid key-repeat events from your terminal, so there is a brief warmup before recording begins. The footer shows keep holding… during warmup, then switches to a live waveform once recording is active.

Enable tap mode with /voice tap. With the prompt input empty, tap Space to start recording. The footer shows a live waveform while recording. Tap Space again to stop.

The dictation key is bound to voice:pushToTalk in the Chat context and defaults to Space. The same binding controls both hold and tap modes. Rebind it in ~/.claude/keybindings.json.

What's Wrong or Missing?

This section mixes two different behaviors:

A. The page documents the push-to-talk key as rebindable

The page correctly says voice:pushToTalk can be rebound in ~/.claude/keybindings.json.

B. But the hint text and usage steps are still described as if they always use Space

That is outdated after the v2.1.136 fix for keyboard shortcut hints reflecting rebound keys from keybindings.json. Once a user rebinds voice:pushToTalk to something like meta+k, the footer hint and the hold/tap instructions should no longer be described as always showing Space.

As written, the page implies the footer hint is fixed text (hold Space to speak) even when the user has configured a different key.

Suggested Improvement

Update this page so the hint and interaction text is binding-aware instead of hardcoding Space.

For example:

Before:

the input footer shows a hold Space to speak hint

After:

the input footer shows the current voice:pushToTalk binding (for example, hold Space to speak by default, or the rebound key from ~/.claude/keybindings.json)

Also update the hold/tap instructions to distinguish default behavior from custom bindings, for example by saying “hold your voice:pushToTalk key” / “tap your voice:pushToTalk key”, with Space called out only as the default.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

Total scope: 1 page affected

Relevant behavior change: Claude Code v2.1.136 fixed keyboard shortcut hints so they reflect rebound keys from keybindings.json.