A Physical Button for Approving What Your Agent Just Did

Slam Buttons is exactly what it sounds like: two full-size arcade buttons mounted on a single plate, wired, macro-definable, and intended for one purpose - approving or killing whatever your agent just proposed with a slap instead of a keypress.

What you actually map them to

Almost everyone maps them to accept and reject, and for good reason: the buttons are large enough to hit without looking, which is the real ergonomic argument for using them over a key you have to locate by feel or by sight. When accept and reject are the two decisions you repeat hundreds of times in a session, a target you cannot miss is worth more than it sounds.

Why a button instead of a key

Everything else in this catalogue is built around efficiency - pedals, macropads, layers. Slam Buttons is built around a different idea: hitting a large button is more satisfying than pressing a key, and that satisfaction is a real reason people review faster with it, even though it is not something we can quantify for you beyond your own experience with it. They are genuine arcade switches, with the long throw and the loud bottom-out that implies, which is exactly what makes them feel different from a keyboard key in the first place.

What it is actually made of

The styling is straight out of an arcade cabinet, and the plate carries the maker's own mark.

When two big buttons are the wrong shape

If your review loop genuinely needs a third or fourth action - not just accept or reject, but something like run tests or skip to the next file - two buttons under-serve you, and a macropad or a multi-pedal foot switch fits the job better. And if you share a desk, a thin wall, or a partner working nearby, the loud mechanical bottom-out is a real trade-off that nothing else in this catalogue asks you to make - worth testing your tolerance for before you commit a permanent spot on the desk to it.

For mapping Slam Buttons into a specific agent's approve-or-reject loop, see our setup guide for Claude Code, or browse the rest of our physical button notes.

Back to blog