A Micro Keyboard for Codex: Which Small Pad Actually Helps

The EM Mini Pad is the closest thing here to a micro keyboard for Codex: a small, heavy anodised aluminium block with five keys and a knurled knob, sitting in the gap where a mug usually goes. It does not integrate with Codex. It sends ordinary keystrokes, so the keys you already press to submit a prompt, approve a diff or stop a run become keys you can hit without looking away from the terminal.

What is a micro keyboard for Codex, exactly?

It is a second keyboard with almost no keys on it. Codex puts you in a short loop: type a brief, wait, read the diff, approve or reject, type the next brief. That loop uses a handful of keys over and over, and on a full board they are scattered across it. A micro keypad or macropad collects them into one small object parked beside the hand that is not on the mouse.

Searches for a Codex micro keyboard, a Codex micro keypad or a Codex macropad all tend to mean the same thing: something small, programmable and permanently in reach. None of these devices know what Codex is. They type into the terminal, and Codex reads the terminal, which turns out to be enough.

Five keys, sixteen keys or three?

The right size depends on how many actions you actually repeat. Count them before you buy.

• EM Mini Pad, $75. Five keys in a 3x2 grid with a knurled knob filling the sixth position. Dual mode, wired over USB-C or unplugged and paired over Bluetooth. Turn the knob to scroll a long Codex output, keep the keys for accept, reject and interrupt.
• KM16 Macropad, $119. Sixteen keys in a 4x4 grid plus one large knob and two small ones. Buy this if your loop is bigger than approve and reject: run tests, commit, switch pane, switch model.
• Vibe Pad, $59. Three keys and a separate clip-on microphone. The cheapest way in and the most compromised: three keys is three keys, and each half is weaker than buying the two halves separately.

Do I have to flash firmware or install a Codex plugin?

There is no Codex plugin and none is needed. The KM16 Macropad remaps through a VIA-compatible page in the browser, so nothing is compiled and no firmware flashing is involved. The smaller pads are programmed with the utility their manufacturer supplies. Codex itself is untouched throughout: you are only choosing which keystroke each key sends, and your existing key bindings stay exactly as they are.

What will a micro keyboard not do?

It cannot tell you when Codex has finished. A pad is an output from your fingers, never an input from the agent, so if the reason you keep switching windows is that you do not know whether the run is done, a pad will not fix that. A Status Light at $45 is the part that answers that question, and only because you point a hook or a script at it yourself.

Why not the Codex-only controller you were looking at?

If you searched for a Codex micro keyboard you have probably found a controller built for Codex alone, and probably found it unavailable. A single-vendor device can offer things a generic pad cannot: a status feed from the tool, matching colours, the vendor's own artwork on the keycaps. What it cannot do is follow you. If you run Codex in one repository and Claude Code, Cursor, Copilot, Gemini CLI or Windsurf in another, a pad that sends plain keystrokes works in all of them on the day it arrives. That is the trade, stated plainly: no deep integration and no vendor-specific status, just the right keys within reach.

If five keys sounds too few for the way you review, read our note on the 16-key macropad for Codex CLI before choosing.