See the run while it is running.
A Claude Code session on your workstation reports what it is doing over a persistent live link. Open it from a browser or a phone and you are looking at the current state of the run, not a summary written after the fact.
// The session keeps running locally. Watching it changes nothing about how it executes.
Knowing beats guessing.
Without a live view, the only honest answer to "how is it going" is to walk back to the machine and read the terminal.
You cannot tell working from blocked
A session that is thinking and a session that stopped for a permission look identical from across the room. One needs nothing from you and the other needs you right now.
Long runs go unattended by design
The point of a long-running agent is that you step away. Live activity is what makes stepping away reasonable rather than a gamble.
Review needs a record of what happened
Seeing the sequence of what an agent actually did is how you judge whether the result is trustworthy before you act on it.
A daemon reports, the control plane relays.
The pieces are deliberately small. A local daemon watches the session, and the control plane fans that activity out to whatever surface you happen to have open.
The daemon observes locally
A lightweight daemon on the machine captures session activity as the session produces it, without taking over the session itself.
A persistent link carries it
The daemon holds a live link to the control plane, so activity travels as it happens instead of waiting for a poll.
Every surface agrees
The browser on your laptop and the phone in your pocket read the same session state, because both read it from the same place.
What the view gives you.
Enough to answer the question you actually have, which is usually whether the run needs you.
Live session activity questions
How live is live session activity?
The daemon maintains a persistent link to the control plane and reports activity as it happens, so what you see reflects the current state of the run rather than a page you have to refresh.
Does watching a session slow it down?
No. Claude Code keeps running locally at its own pace. The daemon observes and reports, and opening the view on another device does not change how the session executes.
What happens if my machine goes offline?
The live link drops and the view stops advancing. The session state you have already seen remains available, and activity resumes streaming when the machine reconnects.
Can I see sessions running on a teammate machine?
Machines and sessions belong to your organization. A member holding a Virex Remote seat works inside that same organization scope rather than through shared credentials.
Does session activity leave my machine?
Activity is reported to the control plane so it can reach the browser or device you are watching from. Your code, your credentials, and execution itself stay on your machine.
Watch the run from wherever you are.
Subscribe to Virex Remote, assign a seat, and install the daemon on the machine your sessions run on.