DevSpec
DevSpec
Sign In
Start Your Project
All Docs/Parallel Autopilot with Remote Control

Parallel Autopilot with Remote Control

A coding agent doesn't need you sitting in front of it. With Remote Control you can hand a running Claude Code session to DevSpec, then steer it — and several more like it — from the DevSpec mobile app while you're walking around with just your phone. Point a few sessions at your project, dispatch work to them by voice, and review the results on the same device. It turns "I'll fix that when I'm back at my laptop" into a fleet of agents working in parallel while you're on the move.

The workflow

  1. Start a few Claude Code sessions on your machine. Open several CLI instances pointed at your project (your laptop keeps running while you step away). Each one is an independent worker.
  2. Run /remote-control in each session. That registers the session with DevSpec — from then on it shows up in the app and can be driven remotely, with its prompts and approvals surfacing as pop-ups you can answer from anywhere.
  3. Drive them from the DevSpec mobile app — by voice. Create an action item straight from your phone (dictate it if your hands are full), then dispatch it to one of your remote sessions. Repeat across the other sessions so several pieces of work are moving at once.
  4. Watch the work land, and test it on your phone. Each session implements its item, commits, and reports back into DevSpec exactly as it would at your desk — and because the result is live, you can test a change (a mobile UI tweak, say) on the very device you're holding, then queue the next item.

Why it's powerful

  • Concurrency. Several sessions work different action items simultaneously, so throughput is limited by how fast you can describe work, not by one agent finishing before the next can start.
  • You're free of the desk. Creating, dispatching, and reviewing all happen from the mobile app — by voice if you like — so a commute, a coffee queue, or a walk becomes productive time.
  • Test where it matters. Mobile improvements are best judged on a real phone. With the agents building remotely and the results flowing straight back into DevSpec, you can verify a mobile change on your actual device the moment it ships, then send back the next instruction.

Tips for running a fleet

  • Give each session distinct work. Dispatch different action items to different sessions. Pointing several agents at the same files at once invites collisions — keep their lanes separate and let each own its change.
  • Lean on voice for capture. The fastest way to keep a fleet busy is to dictate action items as they occur to you; you can always refine the details before dispatching.
  • Keep the laptop awake. Remote Control drives the Claude Code sessions running on your machine, so the machine needs to stay on and online while the agents work.

See also