AI Hotkeys on macOS: Free Keys, Permissions and Dictation
The Left-Hand Pad ($49) is a twelve-key macropad with two rotary knobs, sold for macOS, and it does exactly one thing: it sends keystrokes. Everything after that is macOS deciding what those keystrokes mean. This is a guide to the second half, because on a Mac that is where all the friction lives.
Which key combinations are actually free on macOS?
Fewer than you would hope. Command plus a letter is largely spoken for, either by the system or by whatever app has focus, and a combination that is free in your terminal may already be taken in your browser. The reliable move is to stop competing for them. Program the pad to send keys a normal keyboard does not have, F13 and upward, then bind Claude Code, Codex CLI, Cursor or the ChatGPT desktop app to those. Nothing else on the machine is asking for them.
The next best option is to stack modifiers. Control, Option, Shift and Command held together with one letter is miserable to type by hand and trivial for a macropad, which is close to the whole argument for owning one. You press a single key. The pad presses four.
Why does macOS keep asking for permission?
Because something in your chain is either reading keystrokes it was not sent, or typing keystrokes nobody pressed. macOS treats both as privileged. In System Settings, under Privacy and Security, the two entries that matter are Input Monitoring, for anything watching the keyboard globally, and Accessibility, for anything sending keys into another app. A remapping tool such as Karabiner-Elements wants both, and it installs a system extension you have to approve, usually followed by a restart.
Two details catch people out. Permission is granted per app, so what you allowed for one terminal does not carry across to a different terminal, or to a copy of the same app you moved to another folder. And you are asked once: dismiss the dialogue while you are busy and nothing prompts you again. The symptom is a hotkey that silently does nothing. When a key stops working for no obvious reason, that list is the first place to look, not the pad.
Does a macropad need a driver on macOS?
No. A plain USB keypad presents itself as a keyboard and macOS treats it as one the moment you plug it in. You may get the keyboard setup assistant asking you to press the key next to the left shift so it can work out the layout, which is harmless and can be dismissed. There is nothing to install and nothing to sign in to.
Programming the pad is a separate question from using it. Where a device is configured by a vendor utility rather than by a web page, check which operating system that utility runs on before you buy, because it is not always the one you are sitting at.
How do I set up dictation for a coding agent on a Mac?
Dictation on macOS is a system service, so it types into whatever has focus and your agent cannot tell spoken text from typed text. You choose the shortcut that starts it in the Keyboard section of System Settings. The default has changed between macOS versions, so read what yours actually says rather than trusting a guide. Once you know the shortcut, map it to a key on the pad and you have push to talk.
If you use a third-party dictation tool instead, it needs Microphone permission to hear you and Accessibility permission to type the result into another window. That is two prompts, and the second one is the one people skip.
If you want the pad built around this, the Left-Hand Pad is the one sold for macOS.