AI Hotkeys on Windows: Free Combinations, Drivers and Voice Typing

The KM16 Macropad ($119) is sixteen keycaps on anodised aluminium, with one large knob and two small ones. It is a second keyboard. Windows sees it as a keyboard, and that plain fact decides almost everything about setting it up for Claude Code, Codex CLI, Cursor, GitHub Copilot or the ChatGPT desktop app.

Which shortcuts are actually free on Windows?

The Windows key plus a letter is mostly reserved by the operating system, and the ones that are not reserved today may be tomorrow. Inside a terminal you have a second problem: the shell and the agent both want the ordinary control combinations, and Control plus C is not available for anything you would rather it did.

Two combinations survive. The first is three modifiers plus a letter, Control with Shift with Alt, which almost nothing claims because almost nobody wants to type it. The second is the function keys past the end of a normal keyboard, F13 and upward, which no software is competing for. A macropad can send either without your hand leaving the desk, and that is the point of putting it on a pad rather than memorising it.

Do I need to install a driver?

No. A USB keypad, a macro pad or a foot switch identifies itself as a keyboard, and Windows uses the driver it already ships with. The first time you plug one in there is a short pause while Windows sets it up, then it types. Because it is treated as a keyboard, it also works before you have signed in, which is occasionally useful and occasionally alarming.

Where a pad stores its mapping on the device itself, that mapping travels with it: configure it once, then move it between machines without installing anything. Where a pad is remapped by software on the computer, the mapping lives on that computer only.

Why does my hotkey work everywhere except one window?

Almost always elevation. Windows will not let a program running with normal privileges send input into a window running as administrator. So a remapping utility or a script that you started normally works fine in your browser and your editor, then does nothing at all in the elevated terminal where your agent happens to be running. The fix is to run the helper with the same privileges as the window you want it to reach, or to stop running that terminal elevated.

The other cause is duller: focus. A keystroke goes to the window that has it. If your macropad is meant to accept a suggestion, the editor has to be the active window at the moment you press it, and no hardware can work around that.

What turns an extra key into an action?

Three layers, and you only need one of them to be doing work. The AI tool itself may let you bind a command to a shortcut, which is the tidiest place to do it. Failing that, Keyboard Manager in Microsoft PowerToys will remap a key or a shortcut to another one, and AutoHotkey will run a script when a key is pressed, which is what you want if a single press should send a sequence. A pad that stores its own mapping can skip all three.

How do I dictate prompts on Windows?

Windows has voice typing built in, opened with the Windows key plus H, and it types into whatever has focus. Your agent sees ordinary text. Map that shortcut to a key on the pad, or to a pedal, and you have push to talk without installing anything. It is worth trying that before paying for a dictation tool, because for prompts it is often enough.

If you want the pad in the photograph, that is the KM16 Macropad.