Multi-agent collaboration

Run several agents — and yourself — on one shared memory layer. Each agent has an identity, every memory records who wrote it, and collections can be shared with access control. This is the first of the RememberOS pillars, and it's available today.

Agent identities#

An agent identity is a named API key. Create one key per agent (e.g. support-bot, billing-bot) from the dashboard or the keys API; rotate keys without changing the agent. All of a workspace's agents share the same memory, so what one agent learns, another can find.

Provenance — who contributed what#

Every memory is stamped with the agent that wrote it. Reads return a created_by object, so you always know the source:

{
  "id": "mem_…",
  "text": "Customer prefers email over phone",
  "created_by": { "id": "key_…", "label": "support-bot" }
}

Provenance is server-stamped from the authenticating key (tamper-proof) and the label is cached, so attribution survives even if the key is later deleted.

Shared collections & access control#

By default a collection is open — every agent in the workspace can read and write it (backward-compatible). Add a grant and the collection becomes restricted: only the listed agents, with the permission you give, may access it. This is how "Customer Support" is shared by several agents while "Personal Memory" stays private to one.

Grants API#

Manage access on a collection (requires a write-capable key):

# Share a collection with an agent (this makes it restricted)
curl -X PUT https://rememberos.ai/v1/memory/collections/support/grants \
  -H "Authorization: Bearer $LONGMEM_API_KEY" -H "Content-Type: application/json" \
  -d '{"agent_key_id": "key_…", "can_read": true, "can_write": true}'

# Who can access it? (restricted=false means open to all)
curl https://rememberos.ai/v1/memory/collections/support/grants \
  -H "Authorization: Bearer $LONGMEM_API_KEY"

# Revoke. Removing the last grant makes the collection open again.
curl -X DELETE https://rememberos.ai/v1/memory/collections/support/grants/key_… \
  -H "Authorization: Bearer $LONGMEM_API_KEY"

Access is enforced on every read and write, and tenant-wide search automatically skips restricted collections the calling agent can't read.

Scope today is one workspace (tenant): your agents and you share memory within it. Cross-workspace federation and distinct human vs. agent principals are on the roadmap.