Remote control for AI coding agents
Also called: remote agent oversight, remote session control, steering agents from mobile
What is remote control for AI coding agents?
Remote control for AI coding agents means watching and steering a coding session that is running on your own machine, from a different device. You see activity as it happens, answer the permission and plan decisions the agent stops on, send instructions, and interrupt. The agent never moves.
What is actually being controlled.
Three capabilities, and the second is the one that decides whether a run finishes tonight.
Visibility into a live run
What the agent is doing right now: which files, which tool calls, which subagent, and what it is working through. Without this, an unattended agent is a black box you check on by opening a laptop.
Answering the decisions it blocks on
A coding agent stops to ask before doing something consequential, and then waits. Answering that from your phone turns a two-second decision into a two-second interruption instead of a stalled night.
Steering mid-run
Sending an instruction into a session already in progress, changing its permission mode, or interrupting it. Correcting a run beats discarding it and starting again.
Why remote matters more than it sounds.
Coding agents got good at working for long stretches. Nobody is at the desk for long stretches.
Waiting is the real cost
A permission request takes seconds to answer and can idle a run for hours. The gap between those two numbers is where the time goes.
The desk is not where you are
Overnight and away-from-desk runs are the point of an async agent. They only pay off if the agent can still reach a person.
Reviewable afterwards
Supervised autonomy means something only if who approved what, and when, can be checked later.
Commonly confused with.
Three things that are not this.
Remote agent control questions
What is remote control for AI coding agents?
Watching and steering a coding session running on your own machine from a different device: seeing activity live, answering the permission and plan decisions it stops on, sending instructions, and interrupting. The agent stays where it is.
Does the agent move to the cloud?
No. With Virex Remote the agent runs on your machine under your own model subscription. Code, credentials, and execution stay on your hardware. Only session state and coordination signals leave it.
Is this the same as SSH?
No. SSH gives you a shell. This gives you the session as a structured thing, with its pending decisions surfaced as something you can answer and its activity shown as it happens.
Which coding agent does it work with?
Claude Code is the primary integration for Virex Remote.
What can I do from a phone?
Follow the live session, answer permission and plan decisions, inject a message into a running session, change the permission mode, and interrupt.
Steer the run from wherever you are.
Virex Remote attaches to the Claude Code sessions already running on your machines.