Basic Memory Teams
Basic Memory Teams puts your whole team — and every AI agent they use — on one shared memory. Anything a teammate writes is immediately available to everyone else and to their agents: a decision captured in one person's Claude session becomes context for another's Codex run. Hand work off between humans and agents, and build one connected knowledge base instead of scattered copies.
Workspaces
Your account can have more than one workspace. Each keeps its own projects, notes, and members.
| Workspace | Who can access it | Notes |
|---|---|---|
| Local | Just you, on your machine | No team features; runs entirely on your computer |
| Personal | Just you | Your personal cloud subscription and notes |
| Team | Your team | Shared projects, members, roles, and seats |
In the app, each workspace — personal and every team — appears as its own section in the sidebar. Projects and notes are scoped to the workspace you're in; local projects stay on your machine, reachable from the CLI and MCP alongside them.
Working together
Everyone on the team reads and writes the same knowledge base. A note a teammate saves is available to you — and to your agents — the next time you open it, and every change is listed in the Activity feed with a link to the note it touched.
AI agents as collaborators
AI agents work with the shared knowledge base through MCP. They read the shared knowledge graph for context and write structured observations and relations back into it, so the more your team uses Basic Memory, the better your AI gets at answering from your team's actual knowledge. When an agent writes or updates a note, the change appears in the Activity feed alongside your teammates' edits.
Activity feed
The Activity view in the app keeps you aware of what's happening across the workspace. It shows operations in progress (imports, indexing, large edits) and recent completed changes — from every team member and agent — with direct links to the affected notes.
File history — undo on the file level
Every save creates a new version of a note, automatically. If a teammate overwrites something or an agent edits go sideways, open File history on the note to step back through the timeline, compare any version against the current one, and merge content back in. Restored content saves as a new version, so nothing is ever lost.
See File History for the full reference, or Restore Lost Content for the broader recovery decision guide (File history for a single note, Snapshots for bigger rollbacks).
Security and isolation
Each team gets its own isolated database and file storage in the cloud — there is no shared tenancy at the data layer. Your team's knowledge is physically separated from every other team's. Authentication runs through WorkOS AuthKit for enterprise-grade identity management.