Big Arcade Buttons for Zed: Open the Diff, Not Approve It

Slam Buttons costs $29 and puts two large round red arcade controls on a cream plate. Their output, remapping, connection, host support and sound are not confirmed. Zed offers customizable keybindings, but that does not make its keep, reject or tool-permission actions suitable for two context-free physical targets.

Can two buttons carry Zed's accept and reject flow?

Technically, Zed's current action list includes keep and reject commands. Operationally, two buttons cannot show which hunk, tool request, prompt or focused window owns the next press. A dramatic control may approve the wrong thing more confidently.

Keep review decisions on the keyboard or pointer while the relevant diff or permission card is visible. Do not bind Allow Once, Allow Always, keep, reject or Enter.

How do you bind arcade buttons to keymap chords?

First discover what each control emits in a key viewer. If the events are remappable, assign uncommon neutral chords, then use Zed's keymap editor to translate them under a narrow context. The catalogue does not confirm that this hardware supports that chain.

Safer actions reveal information, such as focusing the Agent Panel and opening its diff. Test every chord with the terminal and message editor active to prove it cannot type text.

Does the slam actually slow you down usefully?

No evidence supports that behavioral claim. A large target can feel deliberate while bypassing the very context that makes a decision safe. It may also add noise or turn careful review into a performance.

Record normal actuation sound in the intended room without publishing a universal acoustic conclusion. The store has no user studies or orders from which to infer better judgment.

What happens when the agent needs more than yes or no?

The two-button model collapses. Zed distinguishes change review, one-time permission, persistent permission, prompt submission and ordinary navigation. The current screen, not a remembered colour or side, identifies the action.

Use one button for Agent Panel focus and one for opening the agent diff only after verified mapping. Test neighboring presses, held input, restart, app switching and loss of focus. Label each safe destination and unplug the plate before leaving an unlocked desk. The Slam Buttons can be a bold navigation panel, but it should never become a binary authorization device for Zed. Use Zed's key context view to inspect where a proposed chord is active, then add a null binding where fall-through could occur. Repeat the negative test in editor insert mode, terminal focus and the message composer. If a remapper cannot distinguish Zed from other applications, avoid ordinary characters entirely. A visible software shortcut remains the safer fallback. Place the plate away from drinks and the keyboard's normal palm area. An inviting arcade target may be pressed by someone who does not know its purpose, so disconnect it or lock the session whenever the desk is unattended. A label cannot replace access control.