Can You Control Claude Code With a Foot Pedal?
Yes. Claude Code runs in a terminal and waits for you to approve or reject the edits it proposes, and approving is just a keystroke. A USB foot pedal that enumerates as a standard keyboard sends exactly that keystroke, so the terminal has no way to tell whether it came from a finger or a foot.
What actually happens between the pedal and the terminal
Pedal Three does not talk to Claude Code, or to any AI tool, directly - it talks to the operating system, the same way any USB keyboard does. Each of its three pedals is independently programmable to send a key, a modifier combination, a text string, or a mouse click. Once a pedal is programmed, pressing it is indistinguishable from typing that same key, which is also why it needs no driver just to use, only to reprogram.
The same is true for Codex CLI, Gemini CLI, or any other terminal agent with the same brief-then-review loop. Because the pedal sends generic keystrokes rather than talking to a specific tool's API, it does not care which agent is running. Claude Code is not a special case here, it is just the one people ask about most.
What you would map three pedals to
The obvious split for a review loop is accept, reject, and push-to-talk if you dictate prompts instead of typing them. That covers the two actions you repeat most while reviewing proposed edits, plus the one action - starting to talk - that otherwise needs a free hand.
- Pedal 1: whatever key you already use to approve a suggestion
- Pedal 2: whatever key you use to reject or ask for a change
- Pedal 3: hold to talk, release to send, if you are dictating
Where a pedal does not help
Claude Code can run a task for several minutes and sometimes asks a question partway through, not only at the end. A pedal fires the exact keys you assigned it and nothing more - it does not watch your screen and does not know a decision point has arrived. It removes the hand movement from approving or rejecting; it does not remove the need to notice that a decision is waiting.
Is it actually worth buying for this
Count how many times you press accept or reject in one review session, multiply by how many sessions you run in a day, and multiply that by roughly how long a hand movement to the keyboard costs you. If the total comes to a few seconds a day, a pedal is not solving a real problem for you yet. If it comes to minutes, or your wrist is what is complaining, it is a fair trade for a wired box that needs no battery and no pairing.
One practical note if you work on a Mac: Pedal Three's configuration tool is built Windows-first, so if you ever want to change what the pedals send, the easiest path is programming it once on a PC and then using it anywhere. The pedals themselves work on macOS with whatever they were last set to send.
For a closer look at wiring all three pedals specifically into a Claude Code review loop, see our setup guide. For other hardware people run alongside Claude Code, browse the Claude Code tag.