Codex, working from what your team already knows.
Codex connects to Virex Memory over MCP, so it draws on the same organization corpus as the rest of your toolchain rather than starting each session from nothing. Virex Remote is a different story, and this page says so directly.
- Not supported: Virex Remote
- Supported: Virex Memory
Remote control for Codex
The honest answer, stated plainly rather than buried.
Virex Remote does not support Codex. 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 Codex
Support follows the Model Context Protocol, so Codex reaches the same memory as every other compatible client with no bespoke integration in between.
Memory tools over MCP
Codex discovers the memory tools through the protocol and uses them while working, instead of waiting for somebody to paste context into a prompt.
Retrieval by meaning
Semantic search returns what is relevant without needing the exact wording an earlier session used.
The same corpus as your other tools
A memory written from Claude Code is retrievable from Codex and the reverse, because scope follows your organization rather than the client.
Maintained automatically
Relevance scoring is refreshed on a schedule and stale memories expire, so nobody owns a curation chore.
Teams rarely standardise on one agent for long. Memory behind a protocol is what stops each new tool resetting what the team knows.
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 Codex
Point Codex at the Virex Memory MCP server so it can read and write your organization memory.
Configuration steps for Codex live in the docs.
Codex questions
Does Virex Memory work with Codex?
Yes. Codex speaks the Model Context Protocol, so it reads and writes the same organization-scoped memory as every other MCP-compatible client.
Does Virex Remote work with Codex?
No. Virex Remote is built around Claude Code sessions specifically. We would rather say that plainly than imply coverage we do not have.
Can Codex and Claude Code share memory?
Yes, and that is the point of putting memory behind a protocol. Both read and write the same organization corpus, so context does not fragment across tools.
Do I need a separate seat for Codex?
No. Seats are per member per product, not per tool. One Virex Memory seat covers every MCP client you use.
What does it cost?
$15 per seat, per month, per product, flat across products. One subscription per organization with a line item per product.
One memory, whichever agent you run.
Subscribe to Virex Memory, assign a seat, and connect Codex alongside everything else.