A 16-Key Macropad for Zed: A Physical Map of Safe Actions

KM16 Macropad costs $119 and provides sixteen keycaps on anodised aluminium, one large rotary control and two smaller ones. VIA remapping is confirmed. The exact key arrangement, knob events, connection, macro support and onboard profile behavior are not, so build from observed input rather than a diagram.

Which Zed actions deserve dedicated keys?

Start with navigation that exposes context: toggle Agent Panel, focus editor, focus terminal, open agent diff, show project panel and move between panes. Zed says almost all functionality is exposed as actions, with current names discoverable in its keymap editor and command palette.

Leave permission, keep, reject, send, file deletion and task execution off the pad. A large surface should improve orientation, not multiply irreversible shortcuts.

How do you bind macropad keys through Zed's keymap file?

First use a key viewer to record what VIA makes each position emit. In Zed, open the keymap editor or `keymap.json`, choose a unique chord and bind it under a precise context such as the workspace or a particular panel. Zed's key context view helps diagnose conflicts.

Add one binding at a time. Restart, change panels and switch projects to verify that the same press never falls through as text.

What should the three knobs control in an editor?

Nothing until turn direction, press behavior and remapping are demonstrated. A verified rotary input might scroll a focused panel or move through a harmless list. It should not change agent permission level, select a model, launch a task or submit a prompt through hidden state.

Keep ordinary scroll and navigation available. Assigning every knob is not a success condition.

Is a macropad redundant if you already use Vim mode?

Often. Vim mode already provides dense keyboard navigation, and another layer adds labels, reach and conflict maintenance. A pad may still help when panel destinations are easier to remember spatially, but modal contexts make broad chords especially risky.

Create a paper layout and simulate it with unused keyboard chords before buying. After setup, test insert, normal, terminal and Agent Panel focus in a disposable project. Photograph the validated map, export no credentials, and review bindings after Zed updates. The KM16 Macropad fits Zed when several safe actions remain useful without modes. Its confirmed VIA support does not make agent approvals appropriate hardware targets. Treat VIA and Zed as separate configuration layers. Give the hardware only uncommon neutral chords, then let Zed translate those chords into contextual actions. That makes application ownership easier to inspect and prevents ordinary letters from leaking into a prompt. Keep a copy of both configurations with dates, but do not include secrets or personal paths. Test every key in a blank document before the Agent Panel is opened. Press neighboring positions, hold each one, rotate each control in both directions and reconnect the device. An undocumented layer or repeated chord is grounds to clear the profile. Visual legends should describe destinations, and inactive caps should remain visibly inactive.