Drive Your Coding Agent from Your Phone

You handed an action item to your coding agent with one click, it's running on your machine — and then you have to step away from your desk. You don't have to lose the thread. Claude Code can make a running session monitorable and controllable from your phone, and DevSpec gives you the command to do it in one tap.

The one command

Claude Code ships an in-session slash command, /remote-control. Run it inside a live Claude Code session and it pairs that session with the Claude mobile and desktop apps — from then on you can watch what the agent is doing, answer its questions, and steer it from anywhere, not just the terminal it's running in.

That's the whole trick for working on the move: the agent keeps doing the work on your machine, but the controls come with you.

Learn more: Claude's own write-up of the feature lives at code.claude.com/docs/en/remote-control.

Where DevSpec helps

/remote-control is a command you run inside your session — it isn't a flag on the launch command, so you can't bake it into the rocket handoff. Instead, DevSpec puts it one tap away: in the same copy-prompt popover that holds the agent prompt, there's a Remote control button (a little phone-and-monitor icon). Tap it and the /remote-control command is copied to your clipboard, ready to paste into your running session.

It shows up only when your active agent is Claude Code — it's a Claude Code feature, so the button stays hidden for tools that don't have it. You'll find it alongside the copy-prompt and rocket icons on action item cards, on the testing page, and on autopilot run views.

The mobile loop

Put the pieces together and you get a workflow that doesn't stop when you leave your laptop:

1. On your phone or laptop, open an action item and hand it to Claude Code (the one-click handoff does this for you).
2. Tap Remote control to grab the /remote-control command and run it in that session.
3. Walk away. From the Claude app on your phone, watch the agent work, answer anything it asks, and nudge it when it needs a decision.
4. When it finishes, it commits and records the implementation back into DevSpec — so the item lands on the testing page ready for verification, exactly as if you'd been sat at your desk the whole time.

You don't have to be in front of the terminal for DevSpec work to keep moving. Start it at your desk, steer it from your pocket.