One tap unblocks an hour of work.
Claude Code stops and asks before it does certain things. Virex Remote brings that request to whatever device you have on you, so the run continues the moment you answer rather than the moment you get back.
// The answer travels to the session. The session never leaves your machine.
A waiting session is the expensive kind.
Permission requests are short to answer and costly to miss. The gap between the two is entirely about where you happen to be standing.
The block is silent
Nothing announces that a session stopped. It simply produces no more output, which looks the same as an agent thinking hard about a difficult step.
The answer takes seconds
Almost every permission request is a decision you could make instantly if you saw it. The delay is access, not deliberation.
Stepping away should be safe
If a run can stall the moment you leave, you never really leave. Remote decisions are what make an unattended agent genuinely unattended.
The request comes to you.
The same request the terminal would show, routed through the live link to the surface you are actually looking at.
The session raises it
Claude Code pauses and asks, exactly as it would if you were sitting at the machine. Nothing about the request is changed or reinterpreted.
You answer from anywhere
Approve or deny from a browser or a phone. Plan decisions work the same way, and interrupt is there when the answer is neither.
The run resumes locally
Your answer travels back down the live link and the session continues on your machine, under your own model subscription.
What a decision carries.
Enough context to answer responsibly, and a record afterwards.
Permission decision questions
What is a permission request?
Claude Code pauses and asks before taking certain actions. Until someone answers, the session waits. Virex Remote surfaces that request wherever you are so the answer does not have to happen at the keyboard.
Does approving remotely change what the agent is allowed to do?
No. It changes where the answer comes from, not what is being asked. The same request, the same options, and the same consequences apply.
Can I deny a request as well as approve it?
Yes. Approve and deny are both available remotely, as are plan decisions, and you can interrupt the current activity outright.
Are remote decisions recorded?
Yes. Security events are audit-logged with the actor, the target, and the timestamp, so a decision made from a phone is as traceable as one made at the machine.
Can an orchestrating agent answer these instead of a person?
Yes. Virex Remote ships a first-party MCP server, so an agent can read the pending decision surface and act on it the same way a person does in the browser.
Answer it from the couch.
Subscribe to Virex Remote, assign a seat, and the requests your sessions raise reach you wherever you are.