A Three-Pedal Foot Switch for Roo Code: Navigation Around Risk

Pedal Three costs $69 and sets three ribbed foot controls on curved steel with a USB cable permanently attached. Roo Code is a VS Code extension whose tools present Save or Reject controls and optional Auto-Approve policy. The pedal's events, remapping and supported systems are not confirmed.

Can a pedal approve a Roo Code action?

Do not build that assumption into a workflow. Roo's visible approval carries the proposed tool and arguments, while a floor press has neither. UI focus and webview behavior can also change which element receives a synthetic key.

Review the request and use the on-screen control. Keep Save, Reject and Enter off all foot mappings.

How do pedals pair with granular Auto-Approve settings?

They should remain separate. Roo's documented policy chooses categories such as reads, edits, approved commands, browser, MCP, mode switching and subtasks. Auto-approval bypasses prompts for selected actions and carries explicit security risk.

Use policy for trusted categories only. A pedal cannot make an unsafe category safe or restore missing context.

Which three bindings earn a pedal each?

Choose reversible editor destinations: focus Roo, return to the code editor and reveal terminal or source control. Discover current commands in VS Code's Keyboard Shortcuts view and test the actual device event first.

Leave a pedal inactive if no third destination is frequent. Do not assign Roo's Auto-Approve toggle, even though an official command exists, because a blind press changes permission behavior.

When has Auto-Approve made pedals pointless?

If Roo no longer pauses on trusted operations, approval pedals have no role. Navigation may still help only when foot input reduces real view switching without confusion or strain. Ordinary shortcuts may remain clearer.

Test each control with source, terminal, search and chat input focused. No event may type or submit. Route the fixed cable away from chair wheels, mark positions and stop after a repeat, focus error or physical shift. The Pedal Three should navigate around Roo's risky slice, never operate it. Give the profile a name that says navigation only and review it after Roo or VS Code updates. Roo's command palette includes an Auto-Approve toggle, so make sure the pedal chords cannot collide with its default or customized shortcut. A successful key-viewer test is only the first layer; repeat it through remapper, editor, focus context and Roo panel state.