Memory your whole team shares.
A decision explained once is a decision everyone else has to ask about. Team memory is a single shared vault: what your team has settled, written once, readable by every member and by the agents they run. Your personal memory stays yours.
$39 per seat, per month. Self-serve up to 20 seats.
Two vaults, kept apart.
Joining a team moves nothing you have written privately. The two are read separately, so a team feed shows the team’s memory and nothing else.
Your personal vault
Everything you capture for yourself, in any tool you connect.
- Visible only to you
- Unchanged when you join or leave a team
- Never surfaced to teammates or their agents
The team vault
What the team has agreed, written deliberately into the team.
- Readable and writable by every member
- Each write carries who made it
- Reaches agents only once approved
Three steps, no admin setup.
Create the team
Name it, and you are its owner. The team gets its own feed, separate from your personal one, and a switcher to move between them.
Invite with one link
Share the invite link, or the code it carries, like CX-A3F7K2. Anyone who has it joins and can read every memory shared inside, so pass it on the way you would a key to the room. The owner can regenerate it at any time.
Write to it
Add a memory from the dashboard, from your editor over MCP, or by importing what another tool already knows. It lands in the team, attributed to whoever wrote it.
A write is not yet a rule.
Anything written to the team arrives pending. A member reviews it and approves or rejects it. Until then it sits in the queue and governs nothing.
Only approved memories are returned to your agents and put into their context. That is what the queue is for: an unreviewed write cannot quietly become a rule the whole team’s agents follow. Every member can review, so the queue never waits on one person.
Two roles. No admin tier.
Deliberately small, so the answer to “who can do this” is always one of two names.
| Role | Can |
|---|---|
| Member | Read the team vault, write to it, review what is pending, and leave the team. |
| Owner | Everything a member can, and remove a member, regenerate the invite code, or delete the team. |
The same vault, over MCP.
Connect your editor once and the team vault is there. Three tools do the team work, and the team is named in every call, so nothing is shared by accident.
list_my_teamsThe teams you belong to and your role in each. Where the team id comes from.
get_team_memoriesThe approved shared memories, filtered by type if you want. Pending ones are not returned.
add_team_memoryWrite to the shared vault. Membership is checked against your own credential, never a name supplied in the call.
Every write is attributed. The person and the tool come from the credential that made the call, and cannot be forged. An agent that names itself is recorded as having said so, and marked unverified, because a name a caller chooses for itself is a claim rather than a fact.
Give your team one memory.
$39 per seat, per month. Unlimited memories, the shared vault, the review queue and roles. Self-serve up to 20 seats; for more than that, talk to us.