Cowork, drawing on your team accumulated context.
Cowork connects to Virex Memory over MCP, so it works from the same organization corpus as your coding agents rather than a separate island of context. This is a Memory-only integration.
- Not supported: Virex Remote
- Supported: Virex Memory
Remote control for Cowork
The honest answer, stated plainly rather than buried.
Virex Remote does not support Cowork. Remote is built specifically around how Claude Code sessions run, pause for permission requests, and gate on plan decisions, and that specificity is what makes the oversight worth having. Claiming generic coverage would make the product worse and the claim untrue.
Memory for Cowork
The protocol is the integration, so Cowork reaches exactly the same memory your coding agents read and write.
Memory tools over MCP
Cowork discovers the memory tools at connect time and uses them during work, with no per-client integration written or maintained.
Retrieval by meaning
Relevant context surfaces without anyone recalling how it was originally phrased.
The same corpus as your coding tools
Context written by a coding agent is available here, which is the practical argument for one organization-scoped memory rather than several.
Maintained automatically
Scheduled scoring and automatic expiry keep what surfaces current as the corpus grows.
Memory is the product that benefits most from being reachable everywhere, because its value compounds with the number of places it is written from and read.
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 to Virex Memory
Checkout starts your organization subscription, or adds Memory as another line item if you already run Virex Remote.
Assign seats
A seat grants a member access. One seat covers every MCP client that member uses, rather than one per tool.
Connect Cowork
Point Cowork at the Virex Memory MCP server so it can read and write your organization memory.
Configuration steps for Cowork live in the docs.
Cowork questions
Does Virex Memory work with Cowork?
Yes. Cowork speaks the Model Context Protocol, so it reads and writes the same organization-scoped memory as every other compatible client.
Does Virex Remote work with Cowork?
No. Remote is built around Claude Code sessions on machines you own, so this is a Memory-only integration.
Is the memory the same one my coding agents use?
Yes. Scope follows your organization rather than the client, so context written from a coding session is available here and the reverse.
Do I need an extra seat for Cowork?
No. Seats are per member per product. One Virex Memory seat covers every MCP client that member uses.
What does it cost?
$15 per seat, per month, per product, flat across products.
Context, wherever the work happens.
Subscribe to Virex Memory, assign a seat, and connect Cowork to your organization memory.