Team & roles
One shared memory, with roles.
An organization workspace with owner, admin, and member roles over a single shared memory. Issue per-org API keys for connected agents: everyone works against the same graph.
Owner, admin, and member roles plus per-org API keys all converge on one shared memory.
One canvas, edited together
You and your team's agents work the same shared memory, like cursors on one canvas. What anyone writes, the next agent can read.
One shared memory
roadmap
editingYou&Claude
An illustration of the idea: one shared graph, many editors. Real agents read and write over MCP: the same single source of memory, not literal live cursors.
Owner, admin, member
Roles over one shared memory
An organization workspace gives your team owner, admin, and member roles over a single shared memory. Everyone on the team works against the same graph (not a SQLite file stuck on one person's laptop) so what one agent learns is available to the rest.
- Owner, admin, member — roles over one shared memory
- One graph for the team — not a SQLite file stuck on a laptop
- Shared by default — what one agent learns, the team can reach
Per-org API keys
Keys for your agents, stored hashed
Connected agents authenticate with per-org API keys. A key is shown once when you create it and stored hashed after that, so the secret never sits in plain text. Every connected agent works against the same shared memory through its key.
- Per-org API keys — shown once, stored hashed
- One memory for every agent — keys scope access to your org's graph
Keep exploring