Agent memory
Share memory between agents, hosts and companies
Agents exchange knowledge that has to last: a decision, a specification, a handoff. The sender writes and shares, and the recipient reads when it next checks in. The agents never connect to each other and never need to be online together.
At a glance
A secure channel between agents
Share any memory with exactly the agents you name, with an expiry and revocation.
A share goes to the agents you name and to no one else.
Across hosts, vendors and companies
Consumer-class memory remembers one person inside one product.
Signed, read-only and checkable
Shared cells are encrypted end to end and signed.
Share any memory with exactly the agents you name, with an expiry and revocation.
Share any memory with exactly the agents you name, with an expiry and revocation. The sender writes and shares; the recipient reads when it next checks in, on any network, anywhere in the world. SAIHM stores the sealed cell and forwards it to the recipient.
Here is how an approved interface spec travels from an architecture agent in London to a build agent in Singapore, which reads it when its day starts:
- Shared cell
- Approved interface spec, v3
- Shared with
- build-agent (Singapore)
- Access
- read-only
- Expires
- in 14 days
- Revocable
- any time
- Signature
- verified, ML-DSA-65
Two agents that need to work together do not have to be wired together. Multi-agent memory explains why a shared memory scales where direct connections do not.
Available today
A share goes to the agents you name and to no one else.
A share goes to the agents you name and to no one else. It covers one item, not an account, a workspace or an API scope that happens to include everything. It runs in one direction, so two agents can cooperate on one thing without either gaining general access to the other.
A share can carry an expiry, and you can revoke it at any time. A collaboration that ends is withdrawn without deprovisioning an integration or rotating a shared credential.
Revocation ends future reads. It cannot retract what a recipient has already read, and no sharing system can. Per-item grants limit the damage of a compromised agent rather than prevent it: the agent reaches what it was granted and nothing else. The memory security page covers the threat model.
Consumer-class memory remembers one person inside one product.
Consumer-class memory remembers one person inside one product. SAIHM is built for enterprise-class agent teams: it gives every agent you run, across models, vendors, machines and companies, one memory it can share. Only your agents, and the agents you grant, can read it.
Between organizations, share exactly what a partnership needs, signed, with an expiry, and revoke it at any time. Each side keeps its own private record, and no central party scores anyone. A robot vendor’s diagnostics agent, for example, reads the fault history it is entitled to and nothing else, and loses that access when the contract ends.
Every memory is sealed before it is stored, so the service holding the ciphertext cannot read what the agents are coordinating about. That is what makes a shared channel acceptable between organizations that are not otherwise willing to share infrastructure.
Any agent that runs local MCP servers, such as Claude Code or Cursor, can add SAIHM with one command. Drop-in adapters cover LangChain, LlamaIndex, LangGraph, CrewAI and AutoGen, a core client serves any Python app, and an endpoint you can run yourself is available. The quickstart shows the setup.
Shared cells are encrypted end to end and signed.
Shared cells are encrypted end to end and signed. Every cell carries a post-quantum signature (ML-DSA-65), so its origin can be checked for as long as it is kept.
A share grants the named recipient read access to a specific cell only. Receiving a share does not change the recipient’s own plan and does not give the recipient the right to share it onward. Only the original cell-holder may extend or revoke access.
Every paid plan includes granular sharing controls: temporary, permanent or syndicate-style, each with revocation.
| Plan | Sharing |
|---|---|
| Free | Included in the fixed one-time lifetime allowance of writes, reads and shares |
| Pro | Yes |
| Pro Fast | Yes |
| Enterprise | Yes |
| Enterprise Fast | Yes |
| Pay-as-you-go | Yes, priced per grantee |
Every paid plan includes granular sharing controls: temporary, permanent or syndicate-style, each with revocation. Allowances by plan, and the pay-as-you-go price per grantee, are on the pricing page.
- Do both agents have to be online at the same time?
- No. The sender writes and shares, and the recipient reads when it next checks in. Shared cells wait until then.
- Can a recipient pass a share on?
- No. Receiving a share does not confer re-share rights. Only the original cell-holder may extend or revoke access.
- What does revoking a share do?
- It ends future reads for that recipient. It cannot retract what the recipient has already read, which is true of every access-control system.
- Does sharing help agents find each other?
- No. Discovery is a directory problem. Sharing lets agents that already know of each other coordinate without wiring; it does not introduce agents that have never met.
No card and no wallet; you need Node.js 20.19 or later.
No card and no wallet; you need Node.js 20.19 or later. Any MCP host that runs local servers can add SAIHM with one command, beside the memory you already use:
npx -y @saihm/mcp-server-pro free-joinKeep reading: swarms and fleets, recipes and levers, enterprise-class memory, enterprise and the Trust Center.