Setting Up a Macropad for Claude Code on Windows

KM16 Macropad is an anodised aluminium pad with sixteen keycaps, one large knob and two small knobs. Its supplier card confirms VIA remapping, which lets it send useful terminal keys to Claude Code on Windows.

Which Claude Code actions are worth a key on Windows?

Use the pad first for terminal navigation, not blanket approval. Escape, return, tab, arrow keys, page movement and an interrupt shortcut are repeated often and remain understandable when printed on a small label. A spare key can open the terminal search or move between tabs if that is part of your normal workflow.

Avoid storing shell commands or permission-changing text until you have lived with the layout. The focused program receives the key. A command intended for Claude Code can land in PowerShell, a text editor or a different terminal pane if focus moved.

How do you remap with VIA on Windows?

Connect the pad by USB, open the VIA configurator and confirm that it recognises the device. Change one position to an unused function key or a plain navigation key, save it, then test in a text field. The listing confirms VIA support, but we have not confirmed every firmware detail or whether every advanced macro behaves identically across revisions.

Prefer simple key codes and uncommon modifier combinations. Windows Terminal and your editor can map those inputs to local actions. Keep a written copy of the original layout so a reset or accidental layer change is easy to undo.

When do you need AutoHotkey on top of VIA?

You do not need it for ordinary keys or modifier combinations. A Windows-side remapper becomes useful when one physical key should behave differently by application, or when you want a terminal-only shortcut without changing the pad itself. Keep those scripts short. A script that types a long command can fire in the wrong window and is harder to audit than a normal keybinding.

Test background scripts with a harmless character first. Locked-down work computers may block installation or background automation, in which case simple VIA bindings are the cleaner route.

Does it work inside WSL and Windows Terminal?

The physical keyboard input reaches Windows Terminal first, then the active shell or program inside the terminal receives the resulting keystroke. That means simple navigation and confirmation keys can reach Claude Code running inside WSL. Windows-level shortcuts may be consumed before WSL sees them, so test each binding in the exact profile you use.

The KM16 Macropad offers more controls than a minimal setup needs. Leave several keys blank until repeated work shows you what deserves them.