Why Slap a Button Instead of Pressing a Key in Cursor?

Slam Buttons is a pair of full-size arcade buttons on one plate, usually mapped to accept and reject, meant for a Cursor review loop where you'd rather slap a button than press a key. The case for it is straightforward: hitting a large button is more satisfying than pressing a key, and that satisfaction is what keeps you moving through review instead of stalling on it. The buttons are also big enough to hit without looking, which is the actual ergonomic argument underneath the fun one, and the reason some buyers keep one hand near the plate through an entire review session rather than reaching for it only occasionally.

What do you map the two buttons to?

Accept and reject, in almost every setup, since those are the two actions you make hundreds of times a day while stepping through Cursor's inline edits and multi-file changes. Two buttons is the right number for a binary decision and not much more; there's no knob, no third key for push-to-talk, and no room for a fourth action the way a pedal or a macropad has.

Are they really arcade-grade, or just arcade-styled?

Genuine arcade switches with full travel and an audible bottom-out, not moulded imitations, which is why they feel different from a keyboard key or a pedal, and it's the whole reason to buy this over a cheaper macro key doing the identical job electrically. The Slam Buttons plate is wired and bus powered, so there's nothing to charge.

How loud is the bottom-out, and does that matter?

Genuine arcade switches have a long throw and an audible, mechanical bottom-out, noticeably louder than a keyboard key or a pedal press. In a private office that's part of the appeal; in an open-plan one, it's the trade-off nobody mentions until the first time you slap accept next to someone on a call. If your desk is shared, that sound is worth weighing the same way you'd weigh dictation volume on a voice keypad before you buy.

Do they need to plug into anything special?

No. They're macro-definable and wired, so once you've mapped the two buttons to whatever accept and reject means in your Cursor setup, they behave like any other input device. Nothing about them understands Cursor specifically; they send the same signal a key press would.

Who should keep their hand on the keyboard instead?

If accept and reject are the only two actions you ever need mapped, and you don't mind reaching a hand slightly off the keyboard to hit a plate, this is a genuinely simple, cheap way to do it. But it only covers two actions; if your Cursor workflow wants a third or fourth, push-to-talk, next file, run tests, a foot pedal gets you there without adding a second device, and keeps both hands entirely free the whole time. The styling is also straight out of an arcade cabinet, and the plate carries the maker's own mark. Compare both against the rest of the Cursor hardware guides.