Questions,answered plainly.
What Virex Memory is, which tools it works with, how retrieval behaves as a corpus ages, who can read what, and how it is billed.
The basics
What is Virex Memory?
Persistent, searchable memory for AI agents. Agents write what they learn while they work, and retrieve it later across sessions, machines, and teammates, all scoped to your organization.
Who is it for?
Software teams working with AI coding agents, particularly teams running Claude Code and other MCP-compatible tooling. The model is team-oriented from the ground up rather than a single-developer tool with sharing bolted on.
How is this different from the memory built into my coding tool?
Memory that lives inside one tool helps that tool only. Virex Memory sits behind the Model Context Protocol, so the same organization memory is available to every MCP-compatible client your team runs, and it stays put when the tools change.
Is Virex Memory a separate product from Virex Remote?
Yes, they are separate products with separate seats. They share one account, one organization, and one subscription, so running both is a second line item rather than a second relationship.
Tools and integration
Which tools can read and write this memory?
Any MCP-compatible client, including Claude Code, Cursor, Codex, Gemini CLI, opencode, and Cowork. Support follows the protocol, so a compatible client that ships tomorrow works with the same memory.
Do I have to use MCP?
No. Virex Memory also offers first-party SDKs and a CLI, and there is a full web interface in the product portal for browsing and managing memories directly.
How do I sign in from a terminal?
The CLI uses a device flow, so you authorize from a browser and nothing long-lived is pasted onto the machine. Step-by-step instructions live in the docs.
Can I wire memory into an agent I built myself?
Yes. First-party SDKs cover that case, and REST and gRPC are available on one host with the same tenancy and access rules as every other client.
How retrieval works
How does search find the right memory?
Memories are embedded as vectors, so retrieval matches meaning rather than exact words. A query about a retry policy can surface the memory describing it even if the phrasing differs.
What is composite relevance scoring?
A scheduled process scores memories so search ranking reflects what still matters as the corpus ages, rather than treating a memory written months ago as equal to one written yesterday.
Does the corpus get worse as it grows?
Lifecycle cleanup expires stale memories automatically, and relevance scoring keeps ranking current. Neither requires someone to run a curation rota.
Can I see and manage what was stored?
Yes. The product portal lets you browse, search, and manage memories directly, so the store is inspectable rather than a black box.
Access and security
Who can read my organization memory?
Members of your organization holding a Virex Memory seat. Memory is organization-scoped by design so knowledge is shared within the team.
How are organizations kept apart?
Per-organization isolation is enforced at the database layer with row-level security, so a query scoped to one organization cannot return another organization data even if application code is wrong.
What happens when someone leaves the team?
An admin removes their seat, which removes their access. The memories their agents wrote stay with the organization.
Does Virex run my agent or see my code?
No. Agents run on your machines. Virex stores what your agents choose to write and serves it back to them. Code, credentials, and execution stay on your side.
Billing
How is Virex Memory priced?
Per seat, per month, at the same flat rate as every other Virex product. The pricing page shows current rates from live plan data.
Do we need one subscription per product?
No. Your organization holds a single subscription containing one line item per product. Adding Memory extends that subscription rather than starting a new one.
Is there a free tier or a trial?
No. Access begins when your organization subscribes and an admin assigns you a seat.
Can someone hold a Memory seat but not a Remote seat?
Yes. Seats are per member, per product, and admins adjust them as the team changes.
Still deciding?
The Virex Memory page covers what the product does and how the pieces fit together.