Skip to content
// FAQ · Virex Remote

How do I run Claude Code on my own machine remotely?

Keep the session running on your own machine and put a control plane over it. A lightweight daemon reports session activity over a live link, so you can watch the run and answer its permission and plan decisions from any browser or device without moving the agent anywhere.

// The detail

Why the obvious approaches disappoint.

People usually try two things first, and both work in a narrow sense while missing what the situation actually needs.

01

Remote desktop and SSH

Both give you access to the machine, and both hand you a terminal to read on a phone. They answer the connectivity question without answering the useful one, which is what the session needs from you right now.

02

Moving the agent to the cloud

A hosted agent removes the machine dependency entirely, at the cost of your code living in someone else environment and your local state being unavailable to it.

03

Keeping the session and adding a control layer

The session stays where your repository, tooling, and credentials already are. What travels is the structure of the run: activity, pending decisions, and your answers.

// How it works

Three moving parts.

Deliberately small, because the agent itself is unchanged.

A daemon on your machine

Installed once on the machine where sessions run. It observes session activity and holds an outbound link to the control plane.

A live link

Activity streams as it happens rather than on a poll, so the view on your phone reflects the current state of the run.

A decision surface

Pending permission and plan decisions appear as things to answer. Your answer travels back and the session resumes locally.

// Stated precisely

What the setup involves.

The account steps are shared with every Virex product. Only the last one is Remote-specific.

AccountCreate your account and organization. One login covers every Virex surface, and each user belongs to exactly one organization.
SubscriptionSubscribe to Virex Remote. Your organization holds one subscription with a line item per product.
SeatAn admin assigns you a Virex Remote seat, which is what grants access to the product.
DaemonInstall the daemon on the machine where your Claude Code sessions run. Configuration steps live in the docs.
NetworkOutbound only. No inbound port, no public tunnel, no exposing the machine.
AgentClaude Code is the primary integration. Remote is built around how its sessions run and pause.
// FAQ

Related questions

Do I need to expose my machine to the internet?

No. The daemon makes an outbound connection to the control plane and maintains the live link from your side. There is no inbound port to open or tunnel to publish.

Does my machine need to stay awake?

Yes. The agent runs locally, so the machine has to be running and connected. If it sleeps, the session pauses with it and activity resumes when it reconnects.

Can I start a new session remotely?

Yes. You can launch a session on a connected machine, either against a project it already knows or a folder you specify.

What can I actually do to a running session?

Follow live activity, send an instruction into it, approve or deny permission requests and plan decisions, and interrupt the current activity.

Is this the same as SSH?

No. SSH gives you a shell and expects you to drive a terminal. This gives you the session structure directly, so pending decisions are things to answer rather than text to read on a small screen.

Keep the agent where it is.

Subscribe to Virex Remote, assign a seat, and install the daemon on the machine your sessions run on.