A Macropad Setup for Zed's Agent Panel
On macOS, Left-Hand Pad provides twelve physical keys alongside two rotary knobs. Zed's customizable keymap can connect its spare inputs to Agent Panel and workspace actions.
Which Zed Agent actions are worth physical keys?
Zed exposes most functions as actions and lets you search them in the command palette or keymap editor. Useful candidates include opening a new agent thread, adding a selection to a thread, moving through a long thread and changing focus between panels.
Keep model changes, tool execution and actions that alter files separate from navigation. The Agent Panel can read, write and run code depending on the configured agent, so physical convenience should not hide the active context.
How do you map a pad through Zed's keymap file?
Make the pad produce spare combinations through a device-specific macOS rule, then open Zed's keymap editor or user keymap file. Bind each spare input to a named action. Zed supports context expressions, so a binding can act only when the Agent Panel or another intended context is active.
Use Zed's key-context view when a mapping behaves differently from expectation. Context-specific precedence is powerful, but it also means the same key can resolve to another action when focus changes.
Do the knobs help with long agent output?
Zed documents keyboard navigation for long threads, including page and endpoint movement when the thread has focus. A knob can send repeated navigation keys if its rotation events are visible to macOS. Test direction and focus before relying on it.
Do not attach file changes or terminal commands to rotation. A fast turn can send many events, while scrolling is reversible and easy to observe.
What does this look like on Linux?
Zed stores user keymaps in a documented configuration path on both macOS and Linux. On Linux, replace the macOS device remapper with keyd or another device-specific input layer, then keep the same Zed action design.
The Left-Hand Pad is sold for macOS, so do not assume its platform support beyond the listing. For macOS, begin with Agent Panel navigation, record each context and leave change-applying actions on the main keyboard until the layout is proven. Keep a three-column record of physical position, operating-system output and Zed action. That record is more valuable than a decorative keycap when a context or default binding changes. Test the key-context view with the editor, terminal and Agent Panel focused. If one input resolves differently, narrow the Zed context instead of adding another operating-system macro. Recheck those contexts after changing your base keymap or panel layout.