opencode, with memory that outlives the session.
opencode connects to Virex Memory over MCP, drawing on the same organization corpus as the rest of your toolchain. Virex Remote is a different story, and this page says so directly.
- Not supported: Virex Remote
- Supported: Virex Memory
Remote control for opencode
The honest answer, stated plainly rather than buried.
Virex Remote does not support opencode. 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 opencode
Because support follows the Model Context Protocol, opencode reaches the same corpus as every other compatible client with nothing bespoke in between.
Memory tools over MCP
Tools are discovered through the protocol, so no integration is written for opencode specifically and none has to be maintained.
Retrieval by meaning
Semantic search surfaces relevant memories without matching the exact words an earlier agent used.
Shared across your team
Memory is organization-scoped, so a teammate agent benefits from what yours worked out.
Maintained automatically
Relevance scoring refreshes on a schedule and stale entries expire, so the corpus does not decay into noise.
Open tooling changes quickly. Memory held behind a protocol rather than inside one client is what makes that churn cheap.
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 opencode
Point opencode at the Virex Memory MCP server so it can read and write your organization memory.
Configuration steps for opencode live in the docs.
opencode questions
Does Virex Memory work with opencode?
Yes. opencode 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 opencode?
No. Remote is built around Claude Code sessions specifically, and we would rather say so than imply coverage we do not have.
Will switching tools later lose my memory?
No. The corpus belongs to your organization rather than to a client, so changing agents does not reset what your team knows.
Do I need a seat per tool?
No. Seats are per member per product, and one Memory seat covers every MCP client that member uses.
What does it cost?
$15 per seat, per month, per product, flat across products.
One corpus, every client.
Subscribe to Virex Memory, assign a seat, and connect opencode.