A 16-Key Macropad for Cursor's Accept/Reject Loop
The KM16 Macropad is a sixteen-key aluminium block with three rotary knobs, remapped entirely through a web-based tool called VIA with no firmware flashing required. Sixteen keys is enough to give a dedicated key to most of the discrete actions in a Cursor session, accept, reject, open the composer, switch files, while the knobs handle whatever you'd otherwise scroll, volume, or paging through a long diff. The weight of the aluminium body is part of the design, not incidental to it: a macropad you're hitting dozens of times a day shouldn't slide around every time you land on an edge key.
What would sixteen keys actually cover in Cursor?
More than the accept-or-reject pair that a pedal or a pair of arcade buttons handles. Split the grid however your session actually breaks down: a handful of keys for the review loop itself, accept, reject, next file, and the rest for the things you do around it, like committing, switching between chat and code, or triggering whatever you run after accepting a change. Sixteen is enough room that you're rarely trading one action for another.
What are the three knobs good for?
Anything continuous rather than discrete. Reviewing a long multi-file diff in Cursor involves a fair amount of scrolling; a knob dedicated to that removes one more reason to reach for a mouse. The other two are free for volume, brush size, or whatever else you'd otherwise turn a scroll wheel for.
Can one layout serve more than one tool?
Yes, and this is one of the stronger reasons to pick a VIA pad over a fixed-function device. Since VIA layers let a held key swap the whole pad to a second set of assignments, you can build one layer for Cursor's accept-reject-file-navigate loop and a second for something unrelated you also do at that desk, design work, spreadsheets, a different editor, without buying a second macropad or living with a permanently mismatched half of your keys.
Do you need to flash firmware to set this up?
No. The KM16 Macropad is VIA-compatible, so you remap it by clicking keys in a browser interface; nothing is compiled, nothing is flashed. VIA also supports layers, meaning a held key can swap the whole pad to a second set of assignments, so one layer can run your Cursor mapping and another can cover something unrelated, like design work.
Is it ready to use out of the box?
Not for this. It arrives with a designer-oriented stock layout that has nothing to do with reviewing code, so plan on spending real time in VIA before the sixteen keys mean anything to your Cursor workflow. If that setup step sounds like more than you want, the five-key EM Mini Pad is a smaller commitment to configure, and a foot pedal needs no key-mapping decisions at all beyond which pedal is which. That twenty minutes buys a mapping built for exactly your Cursor session, rather than someone else's idea of a useful macropad. Compare the options under Cursor hardware guides.