Reviewing Cascade's Steps With Your Feet

Pedal Three is a three-pedal USB foot switch, wired and bus powered, with each pedal independently programmable to send a key, a modifier combination, a text string, or a mouse click. Mapped to accept, reject, and push-to-talk, it puts the two actions you repeat most while reviewing a Cascade plan under your feet instead of your hands.

Why do accept and reject deserve their own pedals?

Because in a multi-step Cascade run you make that decision over and over, once per proposed change, sometimes dozens of times in a single plan, and every one of those decisions normally costs you a hand off the keyboard or the trackpad to reach a mouse or a key combination. Your feet are doing nothing during a code review. Moving the two most repeated actions there means your hands stay where they already are: on the keyboard for the next brief, on the mouse for scrolling the diff Cascade is showing you.

Try the arithmetic before you buy: count how many times you click accept or reject on a Cascade plan over a working day, and estimate a couple of seconds of hand travel for each one. Multiply the two together and you've got a rough sense of how much of your day is spent moving a hand to make a decision your foot could make instead.

What's the third pedal for?

Whatever you want, but push-to-talk is the obvious pairing if you're also dictating briefs, hold the pedal, say what you want changed or answer a clarifying question mid-run, release. Because the pedal sends real keystrokes rather than talking to any API, it works with any input method that accepts typed text, voice-to-text included, and it doesn't care whether the window in focus is Windsurf, a browser, or a terminal.

The base itself is heavy and curved specifically so it doesn't slide across the floor when you press it, which matters more than it sounds like it should once you're hitting a pedal several dozen times an hour.

Does it need drivers or software?

Not to use it. It enumerates as a standard keyboard, so any OS accepts it immediately; a driver only comes into play if you want to reprogram what the pedals send, and that configuration utility is Windows-first. The pedals themselves work fine on macOS and Linux running whatever they were last programmed to send, the easiest path is programming it once on a PC.

Who doesn't need this?

If your Cascade sessions are short and infrequent, a few edits here and there rather than long multi-file plans, the number of accept/reject decisions you're saving a hand movement on may not be large enough to justify a dedicated pedal on the floor. Do the count above honestly before you order.

Specs and ordering are on the Pedal Three product page; if a fourth action would help, see our Pedal Four guide, and for the same setup with another agent, our Claude Code notes. More live under Windsurf guides.

Back to blog