Claude Code, watched and remembered.
Claude Code is the one tool where both Virex products apply in full. Remote gives you oversight of the sessions it runs on your machines, and Memory gives it context that survives them.
- Supported: Virex Remote
- Supported: Virex Memory
Remote control for Claude Code
Claude Code is the primary integration for Virex Remote. The oversight is built around how its sessions actually behave rather than adapted from something generic.
Live session activity
Follow what a running session is doing over a persistent link, from any browser or device.
Permission decisions
Approve or deny the permission requests Claude Code raises, without returning to the machine.
Plan decisions
Approve or deny plan-mode decisions the same way, so plan gates stop stalling unattended runs.
Message injection and interrupt
Send an instruction into a running session, or stop the current activity immediately.
A lightweight daemon on the machine reports session activity and maintains the live link. Claude Code itself keeps running locally throughout, under your own model subscription.
Memory for Claude Code
Claude Code speaks MCP, so it reads and writes the same organization memory as every other compatible client your team runs.
Memory tools over MCP
The agent discovers memory reading and writing through the protocol and uses them mid-task, without a person staging context.
Retrieval by meaning
Semantic search returns relevant memories without needing the wording a previous session used.
Shared with the team
Memory is organization-scoped, so what your session learns is available to a teammate agent.
The same memory is reachable from Cursor, Codex, Gemini CLI, opencode, and Cowork, so switching tools does not reset what your agents know.
What setup involves.
The account steps are the same for every tool. The connection step is where they differ, and that detail lives in the docs.
Create your account and organization
One login covers every Virex surface. Each user belongs to exactly one organization.
Subscribe and assign seats
Subscribe to Remote, Memory, or both. Seats are per member per product and are what grant access.
Install the daemon for Remote
On the machine where Claude Code sessions run, so activity is reported and the live link is maintained.
Connect Claude Code for Memory
Point it at the Virex Memory MCP server so the agent can read and write your organization memory.
Configuration steps for Claude Code live in the docs.
Claude Code questions
Does Virex Remote work with Claude Code?
Yes. Claude Code is the primary integration for Virex Remote. The product is designed around the way Claude Code sessions run, pause for permission requests, and gate on plan decisions.
Does Claude Code work with Virex Memory?
Yes. Claude Code speaks the Model Context Protocol, so it reads and writes the same organization-scoped memory as every other MCP-compatible client.
Does my code leave my machine?
No. Claude Code keeps running locally under your own model subscription. Virex carries coordination, session state, and control signals, and never executes customer code.
Do I need both products?
No. Seats are per member per product, so you can use one and add the other later on the same subscription.
What do I install?
For Virex Remote, a lightweight daemon on the machine where sessions run. For Virex Memory, you point Claude Code at the MCP server. Configuration steps live in the docs.
Both products, one subscription.
Subscribe, assign seats, and connect the machine your Claude Code sessions run on.