An AI Agent Controller for Cursor: Keys Under the Hand That Is Not on the Mouse
The KM16 Macropad is the piece that makes most sense as an agent controller for Cursor: sixteen keycaps in a 4x4 grid with one large knob and two small ones, $119, sitting under the hand that is not on the mouse. Cursor is a mouse-and-keyboard editor, so the win is different from a terminal agent. You keep the mouse where it is, and accept, reject and the shortcuts around them move onto a block you never have to find.
Can a macropad or pedal actually drive Cursor?
Yes, and there is nothing clever about how. Cursor triggers its accept, reject and prompt actions from keyboard shortcuts, and every device here sends ordinary keystrokes. So you have two routes and both work: point the pad at the shortcut Cursor already listens for, or open Cursor's keyboard settings and rebind the action to something the pad sends. No extension is installed in Cursor and nothing runs in the background.
What should each key do?
Start with the actions you repeat without thinking, then stop. A pad with unassigned keys is fine. A pad with keys you cannot remember is worse than no pad.
- Accept the suggested change, and reject, side by side
- Move to the next change or the next file in the review
- Open a new agent prompt, so a follow-up is one press away
- Run the test or build command you type twenty times a day
- The large knob to scroll a long diff, one of the small ones for volume
Pedals or a pad for Cursor?
In Cursor the mouse is genuinely useful, which changes the answer. A pad frees the left hand, and pedals free both hands, which matters more in an editor than in a terminal. The Pedal Three at $69 covers accept, reject and hold-to-talk. Pedal Four at $85 is worth it only if you have a fourth action you genuinely repeat. The Left-Hand Pad at $49 is marketed for macOS, and since a programmable keypad sends ordinary keystrokes it works anywhere, but the KM16 covers the same ground better.
How do I know when Cursor's agent has finished?
This is where honesty matters. Cursor publishes no hardware status feed, so a light cannot read its state. The Status Light at $45 is powered over USB-C and does what a script tells it, which means you need something that can run a command when the work ends. In a terminal agent that is a hook. In Cursor it usually means having the agent run a small command as the last step of its task. If you are not willing to write that, buy the pad and skip the light.
Why not a controller made for one tool?
A vendor-locked controller can do things this cannot: carry the tool's own artwork, and be told directly what the tool is doing. The cost is that it stops being useful the moment your work moves. The same pad, pedal and knob drive Cursor, Claude Code, Codex, Copilot, Gemini CLI and Windsurf, because all any of them see is a keystroke. No integration, no status, no waiting for stock.
For the smaller left-hand version of this setup, see our left-hand macropad guide for Cursor.