Approving Claude Code From Your Phone

Short answer first, because we sell hardware and this is not a hardware question: nothing we make will let you approve Claude Code from a phone. Pedal Three is a USB switch that plugs into the machine in front of you. It is useful in the chair and useless on a train. The rest of this is the software answer, which is the one you came for.

What are people actually asking for?

Three different things, and they have different answers. Some want to kick off a run from somewhere other than the desk. Some have an agent working on a machine that is not the one in their hand, a workstation at the office or a server, and want to keep it moving. Most simply do not want the run they left going to be sitting on an unanswered prompt when they come back. That third group does not need remote control at all. It needs to be told, and that is by far the cheapest problem to solve.

How do people do it today?

The approach that works is the boring one. The approval prompt is a keystroke in a terminal, so anything that puts a terminal on that machine in your hand also puts the approval there. A remote shell over SSH from a phone terminal app is the usual route. Run the agent inside a terminal multiplexer such as tmux or screen and the session outlives your connection, so you can attach from the phone, answer the prompt and detach again. None of that is specific to any agent. It is the same trick people have used to babysit long jobs for decades.

Before you build anything, check whether the tool itself has shipped an official remote or web surface. This area is moving quickly, and a first party option will be less brittle than a shell you maintain yourself.

Is it a good idea?

Often not, and it is worth being blunt about why. Approving from a phone means either reading a diff on a phone screen, which almost nobody does properly, or approving without reading it, which is auto approve with extra steps and a worse view. If you are going to wave it through from the sofa, be honest that this is what you are doing, and think about whether that agent should be running unattended on that machine at all.

The version that does hold up is narrower: you know exactly what it is waiting on, because you set it going and you decided the answer before you left. That is a fine reason to want a phone in the loop. Reviewing seriously from a phone is not.

What is the cheaper fix?

Being told, rather than being able to reach in. If the real goal is that no run sits idle for an afternoon, a notification when the agent stops is enough, and phones are already very good at notifications. The desk equivalent is a light in your eyeline: a Status Light at $45, driven by a script you write, tells you the same thing without a screen, and only helps when you are in the room to see it.

We have written up the whole notification side of this in how do I know when my AI agent is done.