[DOCS] Voice dictation docs say tap mode can use any key, but Caps Lock is unsupported and now errors

Resolved 💬 2 comments Opened Apr 28, 2026 by coygeek Closed May 4, 2026

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

"Rebind the dictation key"

Current Documentation

The docs currently say:

In hold mode, avoid binding a bare letter key like v since hold detection relies on key-repeat and the letter types into the prompt during warmup. Use Space, or use a modifier combination like meta+k to start recording on the first keypress with no warmup. Tap mode has no warmup, so any key works. See customize keyboard shortcuts for the full keybinding syntax.

What's Wrong or Missing?

This is outdated for v2.1.122.

The current docs say tap mode can use "any key," but Caps Lock is not actually usable for voice:pushToTalk because terminals do not deliver Caps Lock as a normal key event. The v2.1.122 changelog says bindings set to Caps Lock now show an error for this reason.

That means the current wording over-promises which bindings are valid and does not prepare users for the validation error or explain why Caps Lock cannot work.

Suggested Improvement

Update the binding guidance to call out this terminal limitation explicitly.

For example, replace the current sentence with something like:

Tap mode has no warmup, so most keys work, but keys that terminals do not emit as key events (for example Caps Lock) cannot be used for voice:pushToTalk and will show an error.

It would also help to add a short note that modifier combinations such as meta+k are a safer choice for voice dictation bindings across terminals.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/voice-dictation | 127-147 | Rebinding guidance currently says tap mode can use "any key" |

Total scope: 1 page affected

Version context: Behavior changed in v2.1.122, where Caps Lock bindings now surface an explicit error because terminals do not send Caps Lock as a key event.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗