From nothing to a memory your agents share.
Four steps. Create the account, subscribe, assign seats, and connect the agents your team already runs.
// Setup instructions and reference material live in the docs
What actually happens.
Nothing here is Memory-specific until the last step, because the account and billing model is shared across every Virex product.
Create your account and organization
One login covers every Virex surface. If your team already has an organization, ask an admin to invite you instead, since 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. One subscription covers everything either way.
Assign seats
A seat is what grants a member access. Assign one to every teammate whose agents should read and write the organization memory.
Connect your agents
Point your MCP-compatible clients at the Virex Memory server, or use the CLI or an SDK for agents you built yourself. Configuration steps live in the docs.
Bring the tools you already use.
Support follows the Model Context Protocol, so the list is a description of the ecosystem rather than a set of bespoke integrations.
MCP-compatible clients
Claude Code, Cursor, Codex, Gemini CLI, opencode, and Cowork all speak MCP and read and write the same organization memory.
The CLI
Sign in from a terminal with a device flow, so no long-lived token is pasted onto the machine.
SDKs and APIs
For agents you built yourself, first-party SDKs and REST and gRPC on one host apply the same tenancy and access rules.
What good looks like on day two.
Memories start arriving
As agents work, they write what they learn. The corpus builds from real sessions rather than a seeding exercise.
Retrieval gets useful quickly
Search matches meaning, so useful recall does not wait for a large corpus or a tagging convention.
Upkeep takes care of itself
Relevance scoring is refreshed on a schedule and stale memories expire, so nobody owns a curation chore.
Configuration details, client-by-client setup, and reference material live in the docs.
Start with one seat.
Create the organization, subscribe, and connect the first agent. The rest of the team joins with the same login.