A Three-Pedal Foot Switch for Zed: Reversible Panel Navigation

Pedal Three costs $69 and sets a trio of ribbed foot controls across curved steel, using a USB cable fixed to the unit. Zed has a customizable keymap that can bind actions and apply context conditions. The pedal's emitted keys, remapping utility and supported systems are not confirmed, so integration starts with observation.

Can a USB foot pedal trigger Zed keybindings?

Only when the operating system recognizes its input and Zed receives a key or chord that the keymap understands. Open Zed's key context view and a separate key viewer before assigning anything. A USB connection alone does not prove keyboard behavior.

Test press, release, hold and repeat events in a disposable project. Keep the normal keyboard and pointer available as recovery routes.

Which three Agent Panel actions should live under your feet?

None should accept, reject or authorize an operation. Zed currently exposes actions such as toggling or focusing the Agent Panel and opening the agent diff. Those reversible destinations are safer candidates, alongside returning focus to the editor.

A foot press lacks the prompt, diff and permission context required for `agent::AllowOnce`, `agent::Keep` or `agent::Reject`. Make decisions by hand after reading the screen.

How do you add pedal-friendly chords to Zed's keymap?

Use Zed's keymap editor or open `keymap.json`, then bind the verified input to an action under the narrowest working context. Zed documents custom sequences and context expressions. Search the command palette or all-actions reference for the current action name instead of copying an old snippet.

Start with one pedal, reload or restart, and confirm that the mapping does nothing outside Zed. Document how to disable it before filling the other positions.

When do pedals fight with Zed's Vim mode?

Vim and Helix modes add modal bindings and context. A chord can behave differently in insert, normal, terminal or panel focus. A broad keymap entry can also override a familiar default. Inspect the live context in every intended mode.

Place the board where each position is distinct without twisting, and route its fixed cable away from chair wheels. If focus changes, a press repeats, or a modal conflict appears, disconnect it before agent work. The Pedal Three belongs beside Zed only as a tested navigation controller. It is not a physical permission system. Give the trial a written stop rule. One wrong application, repeated event or unexplained context change should disable the mapping until its cause is known. Recheck after every Zed or remapper update, because action names and precedence can move. A safe binding must remain safe when the Agent Panel is closed, the terminal is active and a dialog owns focus. Record those cases separately. Do not infer compatibility from a successful press in one window. The complete chain includes device firmware, operating system, remapper, Zed keymap, focus and active context. Each layer needs an observable test. If a normal shortcut already reaches the same panel without strain, the floor controller may add complexity without benefit.