Running a Coding Agent While You're On Camera

Pedal Four costs $85. Four ribbed positions sit side by side across a broad, flat metal base, connected through a USB lead. It may provide hands-free input after its key events and host support are verified. That does not make it safe to approve agent actions while attention is on a video call.

What can you control without your hands showing it?

Microphone push-to-talk, mute or a harmless focus toggle are possible candidates. A pedal may also navigate between two known panes if the state remains visible. The listing does not confirm mappings, remapping software or held press-and-release behavior.

On-camera invisibility is not a design goal. Reliable state, posture and low consequence matter more than whether other participants notice movement.

Which pedal bindings make sense mid-meeting?

Use one meeting control at first and leave the remaining positions inactive. Verify the meeting application's current shortcut and watch its on-screen microphone state. Keep chair wheels and walking paths away from the cable and plate.

Do not mix a meeting layer with an agent-command layer. A focus mistake should never turn mute into submission or shell execution.

What are the risks of approving while distracted?

Approval requires understanding the proposed tool call, changed files, destination and side effects. A call divides attention and can hide screen detail. Foot activation removes deliberate friction and makes accidental presses harder to attribute.

Pause consequential agent work until review is possible. No pedal should approve, reject, continue, deploy, delete or press Enter on generated content.

Is this actually a good idea?

Running a low-risk read or test during a meeting may be reasonable when it cannot mutate external systems and the session can wait. Trying to supervise active changes through a four-button floor interface is not. Use notifications to remember the session, not controls to rush it.

The Pedal Four is best evaluated for reversible meeting input. Confirm compatibility, test the real floor position and keep agent decisions on a visible, deliberate interface after the call. Set a rule before joining: the agent may finish its current reversible step and wait. Disable any automation that continues through permission prompts. If a notification arrives, record a note for later instead of interacting covertly. After the meeting, return through the transcript, inspect the working tree and rerun relevant checks before granting any next action. Attention is the scarce control surface here. Use the pedal only after a seated mock-up proves each position reachable without looking down or moving the chair. Disconnect it fully when switching back to agent review.