由Notion支持的AI内存。

背景故事为你的AI助手提供了一个持久的共享记忆：它会存储 对话、决策、后续任务以及持久关系，作为 Notion 任何队友或特工会话都能读取的页面。任何你使用过的 模型上下文协议（Claude Code， Codex、光标、OMP及其他MCP主机）可以调用、保存并推理 同一个保险库，因此上下文得以保留/clear、新分支和切换 人们。

在底层，Lore将一个保险库组织成五个核心Notion数据库： 项目、主题、内存、实体（规范句柄解析），以及 事实。同一域服务支持三个表面：一个MCP服务器 AI助手、人类的CLI以及自动线路挂钩命令 上下文加载和会话保存到支持的主机中。

快速启动

1.安装背景故事

从 npm 安装（推荐）

公共 npm 不需要注册表配置或包令牌。

从源头构建

npm link 使 lore 在你的 PATH 上从克隆体全球开放。 运行lore --version确认任一安装路径，然后继续使用 步骤2如下。

Lore

AI memory backed by Notion.

Lore gives your AI assistants a persistent, shared memory: it stores conversations, decisions, follow-up tasks, and durable relationships as Notion pages that any teammate or agent session can read back. Anything you use with the Model Context Protocol (Claude Code, Codex, Cursor, OMP, and other MCP hosts) can recall, save, and reason over the same vault, so context survives /clear, new branches, and handoffs between people.

Under the hood, Lore organizes a vault into five core Notion databases: Projects, Topics, Memories, Entities (canonical-handle resolution), and Facts. The same domain services power three surfaces: an MCP server for AI assistants, a CLI for humans, and hook commands that wire automatic context loading and session saving into supported hosts.

Quick Start

1. Install Lore

Install from npm (recommended)

npm install -g @notionhq/lore
# or
npm install -D @notionhq/lore

Public npm requires no registry configuration or package token.

Build from source

git clone https://github.com/makenotion/lore.git
cd lore && npm install && npm run build && npm link

npm link makes lore available globally on your PATH from the clone. Run lore --version to confirm either installation route, then continue with step 2 below.

For project-local installs, run npx lore from inside the project or add a lore script to package.json. See docs/dev-dependency-install.md for the Yarn PnP wiring and path-portable setup teams use to share assistant config across a repo.

2. Join an Existing Shared Vault

Most operators should join an already initialized shared vault. A Lore vault is a Notion page that already contains the five databases (Projects, Topics, Memories, Entities, Facts). Joining that vault means pointing your local .lore.yaml at the shared vault.pageId; do not run database initialization against a shared page that your team lead has already bootstrapped.

.lore.yaml is local-only. Keep it out of version control, and distribute shared values such as vault.pageId through onboarding docs instead of committing config. This is the current policy even for credential-free shared vault config and supersedes older changelog notes that allowed intentional committed config.

Notion page IDs are access locators, not bearer credentials: knowing a page ID does not grant access unless the caller’s Notion token can already read that page. Even so, keep vault.pageId out of version control so external clones of a public repo don’t auto-target a maintainer’s vault. If a personal or accidental page ID lands in git history, scrub the working tree and decide with the page owner whether to replace the page or rewrite history.

Internal Notion engineer + shared vault

Use Lore’s ntn-backed auth flow. It auto-installs ntn when needed, runs