Your agent stopped to ask. You are not at the desk.
Claude Code runs on your workstation and regularly pauses for a permission approval or a plan decision. Virex Remote lets you watch those sessions and answer them from anywhere, while the agent keeps running exactly where it is.
// Claude Code keeps running locally. Virex coordinates, and never executes your code.
Unattended agents still need an attendant.
The promise of a long-running agent is that you can walk away. The catch is that any run can stop for a decision two minutes after you do, and then it simply waits.
The session stalls where you left it
A permission request or a plan gate blocks progress until someone answers. If that someone is away from the machine, the agent sits idle rather than working.
You cannot see what it is doing
Without a view into the run, the only way to know whether an agent is working, blocked, or finished is to walk back to the terminal and look.
Nobody else can help
A teammate cannot pick up a stalled session on your machine, so work waits for one specific person to come back.
A daemon on your machine, a live link to the control plane.
Install a lightweight daemon on the developer machine. It captures session activity and maintains a live link. From any browser or device you follow the run in real time and drive it.
It runs where you do
Claude Code itself keeps running locally throughout. Virex Remote observes and relays, and does not move your work onto someone else infrastructure.
The link stays live
Session activity streams to the control plane as it happens, so the view you open on a phone matches the terminal you walked away from.
You keep the controls
Inject a message, approve or deny a permission request or plan decision, or interrupt the current activity. The session responds as if you were sitting in front of it.
What you can do from anywhere.
Nine capabilities, all grounded in what ships today.
Live session activity
Follow what a running Claude Code session is doing over a persistent live link, as it happens.
Read moreRemote permission decisions
Approve or deny a permission request without being at the machine that raised it.
Read moreMessage injection
Send instructions into a running session from anywhere and have them land as if you had typed them.
Remote plan decisions
Approve or deny plan-mode decisions the same way you handle permissions.
Interrupt
Stop a session current activity immediately when it heads somewhere you did not intend.
Connected machines
See the machines and agents linked to your organization, and which sessions belong to which.
Billing-safe by design
Virex drives the interactive CLI, never a metered programmatic entry point, so a long run costs the same flat seat.
Read moreControl-plane security
Code, credentials, and execution never leave your machines. Virex carries coordination and state.
CLI and MCP server
First-party tooling with device-flow login, so an orchestrating agent can follow a run the way you do.
New to the vocabulary? A permission request is the pause these capabilities exist to answer, and the interactive CLI versus Agent SDK distinction explains why a long run costs the same flat seat.
Remote control without handing over the machine.
Remote is a control plane. That distinction is the security model, not a marketing line.
Execution stays local
Your agent runs on your hardware under your own model subscription. Virex never executes customer code.
Credentials stay local
Machine credentials and model accounts remain on your side of the link. Virex carries control signals and session state.
Isolation is enforced in storage
Session records are scoped to your organization with row-level security at the database layer, not application checks alone.
Actions are audit-logged
Security events are recorded with the actor, the target, and the timestamp, so a decision made from a phone is as traceable as one made at the keyboard.
Teams that leave agents running.
If you want the situation rather than the feature list, start with code from your phone. If you are weighing us against something specific, the comparisons cover Omnara and Devin.
Developers running long jobs
You start a refactor and step away. The run continues, and the decisions it raises reach you instead of waiting silently.
Teams driving several sessions
More than one session at a time means more than one thing that can block. Connected machines and live activity give you one place to see all of it.
On-call and out-of-hours work
When a run needs an answer at an inconvenient hour, answering it does not require getting back to a specific desk.
Virex Remote questions
Which coding agent does Virex Remote work with?
Claude Code is the primary integration. Remote is designed around the way Claude Code sessions run, pause for permissions, and gate on plan decisions.
Does my code leave my machine?
No. Claude Code keeps running locally and your code, credentials, and execution stay on your machines. Virex carries the coordination, session state, and control signals that make the remote view work.
What do I install?
A lightweight daemon on the machine where your sessions run. It captures session activity and maintains the live link to the control plane. Setup instructions live in the docs.
What can I actually do to a running session?
Follow its activity live, send it an instruction, approve or deny a permission request, approve or deny a plan decision, and interrupt the current activity.
Can a teammate watch or drive my session?
Access follows your organization and the seats within it. Sessions and machines belong to the organization, so teammates holding a Remote seat work within the same account rather than through shared credentials.
Can an agent drive Remote instead of a person?
Yes. Remote ships a first-party MCP server, so an orchestrating agent can follow session activity and act on the decision surface the same way a person does in the browser.
What does it cost?
$15 per seat, per month, the same flat rate as every other Virex product. Your organization holds one subscription with a line item per product, and a long unattended run costs no more than a short one.
Stop being the reason the run is waiting.
Subscribe to Virex Remote, assign a seat, and install the daemon on the machine your sessions run on.