Setting Up a Macropad for Codex CLI on Windows

For a Windows Codex desk, KM16 Macropad puts sixteen keycaps beside one large knob and two small knobs on an aluminium body. Its confirmed VIA support makes it suitable for sending plain, inspectable keybindings to Codex CLI on Windows.

Does a macropad work with Codex CLI inside WSL?

Yes for ordinary keyboard input. The pad sends a key event to Windows, Windows Terminal receives it, and the active program inside the terminal sees the resulting keystroke if Windows has not consumed the shortcut first. WSL does not need to know that the event came from a separate pad.

The practical failure is focus. If another Windows application is active, that application receives the key. Test every binding in the Windows Terminal profile, shell and pane layout you actually use. A shortcut that works in one terminal can be intercepted in another.

How do you set the bindings with VIA?

Connect the pad over USB and confirm the VIA configurator recognises it. Change a single position to a plain navigation key or an uncommon modifier combination. Save, close the configurator and test in a harmless text field. The supplier card confirms VIA remapping, but we have not independently confirmed every advanced macro or firmware revision.

Keep a copy of the starting layout. Use labels that describe the output, not your hoped-for Codex action. A key labelled escape remains understandable when you use the pad in another terminal program.

Which approval keys matter most in Codex CLI?

There is no single map that is safe for every approval. Codex can ask about command execution, file changes, network access and other permissions depending on configuration. The visible choices and their consequences matter more than the letter used to select one.

Use physical keys for navigation between choices and for return only if you still read the highlighted decision. Keep permission-mode changes and any broad approval option off the pad. Hardware should help you review, not turn review into a reflex.

Where does AutoHotkey still help?

A Windows-side remapper can make one pad key behave differently in Windows Terminal than it does in another application. It can also translate a spare combination when the pad firmware cannot express the shortcut you want. You do not need it for normal key codes that VIA already sends.

Avoid scripts that type long shell commands or approval sequences. They are hard to inspect at the moment they run and can land in the wrong window. The KM16 Macropad gives you ample controls, but a small set of transparent bindings is the safer Codex setup.