A Three-Pedal Foot Switch for Cline: Navigate, Do Not Approve

Pedal Three costs $69. It uses three ribbed foot controls across a curved steel base and a USB cable fixed to the board. Cline runs inside supported editors and presents approval controls in its interface. The pedal's events, remapping and platform support are unconfirmed, and a foot switch cannot assume access to webview buttons.

Can a foot pedal press Cline's Approve button?

Not reliably from the documented facts. Cline shows Approve and Reject buttons for gated actions, but its user documentation does not establish a universal editor command for those buttons. Mouse coordinates, Tab counts and synthetic Enter depend on focus and UI layout.

Do not automate that path. Read the proposed file change or command and decide with the visible control.

Which editor keybindings can pedals actually reach?

A pedal may emit a keyboard event that the host editor can bind, but both parts need verification. Reversible candidates include focusing the Cline view, returning to the editor and focusing a terminal or diff. Discover existing commands through the editor's Keyboard Shortcuts interface.

Test only neutral chords in an empty project. Make the mapping application-specific and preserve ordinary shortcuts.

How do three pedals split across approve, reject and focus?

They should not. Use focus destinations only, and leave a position inactive if there is no third safe need. Approval meaning varies by tool call: reading, editing, commands, browser and MCP actions carry different scope.

A physical yes or no without the requested action is missing the most important information. Keep submission and mode changes off the floor.

When is Auto Approve better than any pedal?

Cline's Auto Approve settings evaluate categories per tool call and can keep higher-risk operations gated. That explicit policy is more inspectable than imitating clicks with hardware. It still needs careful configuration; Cline recommends starting with project reads and leaving broader actions off until there is a reason.

Do not enable broader automation merely to avoid using a pedal. Checkpoints can help recover files, but they do not reverse every external side effect. Test press, release, repeat, focus loss and reconnect with disposable content. Route the captive cable away from chair wheels and stop if the base moves or posture suffers. The Pedal Three belongs in a Cline setup only as verified editor navigation, never as an approval surrogate. Review Auto Approve categories separately from editor shortcuts, because changing one should not silently change the other. Enable Cline notifications when approval is required if that solves the attention problem without a peripheral. Checkpoints are a file-state recovery aid, not permission to press blindly: terminal commands and network actions can have effects outside the saved workspace. Mark the three positions on paper and test reach without looking down. If the fixed cable crosses a walkway, the controller is unsuitable until placement is corrected. A missed or duplicate press must become a stopped test, never a reason to add timing delays or automatic retries.