Notion Shared Agentic Context Vault
The Notion Shared Agentic Context Vault is a design pattern for using a Notion workspace as durable, shared memory that multiple AI agents and people can read, write, and govern. It addresses a structural gap in agent systems: knowledge accumulated during a session normally disappears when the session ends, and memory that does persist is usually local to one harness, model provider, or machine. The vault moves context into a workspace that outlives all three, so that "there’s a durable, shared place to remember what matters"[^c1].
The pattern is realized in two overlapping forms. Lore, an MIT-licensed reference implementation, organizes a vault into five relational databases — Projects, Topics, Memories, Entities, and Facts — and exposes them through the Model Context Protocol. Notion's packaged agent setup instead configures a whole workspace as a shared context layer, with an Agent Operating Guide, a private Memories database, and a shared Skills library. Both treat context as an editable artifact rather than a transcript; Lore was built as "shared, persistent memory for agents, backed by Notion"[^c2], and the result is "a multiplayer knowledge system rather than a single-player solution"[^c3]. Notion describes the same outcome as agents that "can now share one workspace-based brain instead of rebuilding context from scratch in every app"[^c5].
A crucial distinction runs through both forms: Notion's default Memories database is personal, not organizational. "Memories are private to you"[^c13], and the store is "separate from the Skills and Custom Agents your team can share; it is not a team-wide memory database"[^c12]. A genuinely shared vault therefore requires a team-owned layer — Lore, shared pages, or an agreed workspace structure — in addition to any personal memory each user enables. The November 2026 announcement that "ChatGPT・Claude・Muse・Botなど複数のAIエージェントが同じ「Memories」データベースを読み書きできる"[^c11] describes continuity across a single user's clients as much as collaboration across a team.
The capability arrived in stages. Notion 3.8 paired MCP connections with administrative controls, column-level permissions, attribution in version history, and a Skills API, recasting continuity as "shared context: documents, task records, permissions, and the history of changes"[^c7]. Memory sync went live on 19 October 2026, with "Memory sync is live today, with skills via MCP coming soon"[^c6]; the fuller two-stage schedule confirmed that "メモリ同期は2026年10月19日から提供開始、MCP経由のスキルは「近日提供」という段階です"[^c10]. The same period exposed the agent itself as an API: the Agent APIs became generally available on 2 November 2026[^c21], letting external applications start sessions with Custom Agents or the personal agent while distinguishing what a personal access token can reach from what a connection token can[^c22]. A public campaign on 4–5 November extended the pitch to mainstream assistants. The mechanics now depend on several layers working together: agents retrieve a bounded slice of context through search, property filters, relations, and an index rather than loading the whole store; typed properties and relations make records queryable; provenance and version history make them verifiable; permissions and column-level controls make sensitive material selectively visible; and maintenance processes expire stale facts, merge duplicates, and flag contradictions.
The evidence for the pattern is real but conditional. In a paired evaluation, "Without memory, the agent passed 82. With relevant memory loaded in, it passed 102"[^c15], yet "Memory helped in 27 cases. It hurt in 7"[^c16], and Notion's own pilot found that "Only 55 to 60 percent of what piled up was worth keeping"[^c14]. A vault is therefore as much an operating discipline as a storage design: "any teammate or agent session can read back"[^c4] the same records, but only if those records remain specific, current, and retrievable. It is also not a panacea or a security shortcut: "Notion's shared brain is useful, but it is not magic memory and it is not a permission bypass"[^c8]. Custom Agents in particular carry independently granted access with no inheritance[^c18], prompt injection "no system offers perfect protection against all attacks."[^c17], and operational costs continue in the form of credits[^c19] and the need for external backup because Notion provides none natively[^c20]. A critical counterpoint further argues that consolidating every agent into one memory is not the only option, and that "引き継ぐことと、置き換えることは同義じゃない" — inheritance and replacement are not the same[^c9]. The open questions concern scale, cross-team sharing, portability, attribution, and the security of a store that both people and agents can write.