Slapping Accept and Reject in Codex CLI
Slam Buttons are two full-size arcade buttons on a single plate, wired and macro-definable, intended for exactly one job: accept and reject. Codex CLI's review loop comes down to those two decisions made over and over, and a button you can hit without looking at it turns out to matter more than it sounds like it should.
What do you actually map the two buttons to?
Accept and reject, in almost every case, there isn't really a third obvious action for two buttons, and trying to overload one with a double-press just slows you down. Slam Buttons send whatever keystroke you define, so mapping them is the same as mapping any other keyboard-emulating hardware: pick the key you already use to approve or reject a Codex CLI suggestion, and assign it to a button.
Why would a button feel different from a key?
Genuine arcade switches have a long throw and an audible bottom-out, unlike a keyboard key's short, quiet travel. That's not a spec that shows up on a chart, but it's the actual reason people like these: hitting a large button is more satisfying than pressing a letter, and that satisfaction is what makes you review a little faster over a long session. The buttons are also big enough to hit without looking, which is the real ergonomic case, you can keep your eyes on the diff and just slap the button in your general direction.
What's the honest limit of a two-button device?
It's exactly two actions. The moment your Codex CLI workflow needs a third repeated action, re-running tests, jumping to the next file, dictation, you've outgrown Slam Buttons and need something with more keys, like a foot pedal or a macropad. Buying these expecting to grow into more mappings later is the wrong reason; buy them because accept and reject really are the whole job.
Does it need power or pairing?
No. It's wired and bus powered, so there's nothing to charge and nothing to pair. Plug it in and the two buttons are live.
There's also nothing to remap through software beyond assigning the two keystrokes once; there's no browser configurator and no layers to learn, which is part of the appeal if the KM16's twenty-minute VIA setup sounds like more configuration than a two-button device should need.
Who should skip Slam Buttons?
Anyone who already knows two actions won't be enough, if you're reviewing agent output but also managing panes, re-running checks, or dictating, buy a device with more mappings from the start rather than this one first and a macropad six months later. It's also worth knowing the styling is straight out of an arcade cabinet, and the plate carries the maker's own mark. If two big, satisfying buttons are genuinely the whole review loop for you, this is the cheapest and most direct way to build it. For more of this lineup, see the Codex CLI tag.