Voice input hotkey picker should support Caps Lock, individual F-keys, and custom key bindings

[tnederlof]

Summary

The voice input hotkey picker in Settings > Agents > Warp Agent > Voice offers a fixed list of modifier/function keys. Users cannot bind voice activation to other ergonomic keys such as Caps Lock or individual F-keys (F1–F12), even though those keys are well-suited to a push-to-talk use case and are commonly used for this purpose in other apps.

Problem

The current pre-defined key list is:

• None
• Fn
• Option (Left / Right)
• Control (Left / Right)
• Command (Left / Right)
• Shift (Left / Right)

Keys like Caps Lock and individual F-keys (F1–F12) are absent. Both are low-conflict and ergonomically convenient: Caps Lock is commonly remapped for push-to-talk in voice/video apps, and F-keys are isolated from the normal typing flow and a natural hold-to-record key. There is no way to supply a custom key outside the fixed list.

Desired workflow

1. Open Settings > Agents > Warp Agent > Voice.
2. Open the hotkey picker dropdown.
3. Select Caps Lock, an individual F-key (e.g. F13), or any other bindable key not currently listed — or press a custom key to bind it directly.
4. Voice recording activates/deactivates on press-and-hold of the chosen key as expected.

Expected behavior

Users can bind voice input to any key that macOS exposes as bindable, including at minimum Caps Lock and individual F-keys (F1–F12), either through an expanded dropdown or a press-to-capture custom binding field.

Actual behavior

The hotkey picker only exposes a fixed list of ten modifier/function keys. Caps Lock and individual F-keys are not available, and there is no free-form binding option.

Warp version

v0.2026.04.27.15.32.stable_03

Operating system

macOS 26.4.1 (Build 25E253)

[oz-for-oss]

@tnederlof

Here's what I found while triaging this issue:

This looks like a current feature gap rather than a one-off configuration issue: the Voice Input setting currently exposes only the built-in modifier/Fn choices. The request is actionable as an expansion of the voice activation key picker and/or a custom key-capture flow.

Maintainer details

I concluded that voice input activation key selection is currently limited to a fixed modifier/Fn enum, so Caps Lock, individual F-keys, and free-form key capture are an unsupported but actionable enhancement..

Triage summary

This is an enhancement request for the Voice Input activation key picker, not an evidence-backed runtime bug. The reported limitation is confirmed by the current code: VoiceInputToggleKey is a closed enum with only None, Fn, and left/right Alt/Control/Super/Shift variants, and AISettingsPageView builds the dropdown from VoiceInputToggleKey::all_possible_values().

Likely implementation area

• app/src/settings/ai.rs defines the persisted VoiceInputToggleKey variants, display names, to_key_code(), and tooltip/keystroke helpers.
• app/src/settings_view/ai_page.rs builds and handles the Voice settings dropdown via SetVoiceInputToggleKey.
• app/src/editor/view/element.rs, app/src/editor/view/mod.rs, and app/src/root_view.rs route the configured key to start/stop voice input.
• crates/warpui/src/windowing/winit/event_loop/mod.rs currently converts only modifier/Fn keydown events into ModifierKeyChanged, which is the path used by the voice toggle handler. F-keys and Caps Lock would likely need either broader key press/release handling or a separate capture mechanism, not just additional enum variants.
• crates/warpui/src/platform/mac/keycode.rs and crates/warpui_core/src/platform/keyboard.rs already contain KeyCode entries for Caps Lock and many F-keys, so the lower-level key representation exists at least in part.

Duplicate check

I checked all open non-PR issues. Related issues exist for voice shortcuts (#9006), global hotkey key support (#2716), and broad keyboard accessibility (#6642), but I did not find two or more open issues that request this same Voice Input picker expansion to Caps Lock/F-keys/custom capture, so this should not be marked duplicate.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz