B
botzrDev/dreamd
Portable, local-first memory layer for AI coding agents
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
官方说明Portable, local-first memory layer for AI coding agents. One .agent/ folder shared across Claude Code, Cursor and Cline over MCP. Plain files, no vector DB.
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"botzrdev-dreamd": {
"command": "npx",
"args": ["-y", "dreamd-mcp"]
}
}
}解析自我们于 2026-10-29 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"botzrdev-dreamd": {
"command": "npx",
"args": ["-y", "dreamd-mcp"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio botzrdev-dreamd -- npx -y dreamd-mcp
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 6 ★ · botzrDev/dreamd · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-10-29 · 最近见到 2026-11-14 · 共见到 17 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 6 ★ · 1 个来源 · repo
- 安装
npx -y dreamd-mcp
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx -y dreamd-mcp。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: 记忆增强。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
botzrDev/dreamd；我们收录于 2026-10-29；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# dreamd
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
The plain files in your repo are the memory. dreamd is the local server that reads and writes them.
Drop a .agent/ folder in the project. Claude Code, Cursor, Cline, and other MCP-aware harnesses share it. What one agent learns, the next already knows. You can cat, grep, and git diff every byte. Durable appends go through MCP / the daemon so the writer stays single-writer.
This is not "another memory product." It is a storage-model wedge: the filesystem is the source of truth, and the MCP tools (searchnodes / appendnode) are a thin interface over those files.
Open core: Apache-2.0 core today, self-hosted only. Premium features may ship later. Do not read this as free-forever for everything.
bash
npx -y dreamd-mcp setup # scaffold .agent/ and wire your harness
npx -y dreamd-mcp # MCP server (stdio) — what the harness spawns
> First run prints a local-only privacy disclosure. setup prompts for harness choice when it has a TTY.
## The moment it earns its name
Recorded live, sped up 1.5x: Claude Code writes the lesson, OpenCode reads it back through the same .agent/ folder. Tape: docs/assets/demo.tape.
No re-explaining. No re-pasting. Same .agent/ folder, every harness.
## Install
### npm (recommended)
bash
npx -y dreamd-mcp setup # scaffold .agent/ + write the harness MCP config
npx -y dreamd-mcp # MCP server (stdio) — your harness spawns this
stdio stays the default transport. dreamd mcp --bind 127.0.0.1: is the opt-in Streamable HTTP server at /mcp. It is unauthenticated, and it is only in source builds with --features mcp-http — see docs/mcp-transports.md.
Requires a project root sentinel (.git/, Cargo.toml, package.json, or pyproject.toml).
setup prompts when it has a TTY. In scripts and non-interactive shells, pass --yes --harness claude|cursor|both (--harness none or --no-write-mcp scaffolds without touching any MCP config).
### Cargo / from source
bash
git clone https://github.com/botzrDev/dreamd.git
cd dreamd
cargo install --path crates/dreamd-cli
See CONTRIBUTING.md for the full dev setup.
## Quick start ( on the npm path, or cargo install --path crates/dreamd-cli if you want the dreamd binary. The shim forwards only some subcommands (npx -y dreamd-mcp --help lists them); recall, score, status, archive, and migrate need the dreamd binary.
Adapters: Claude Code · Cursor · Cline
## What dreamd writes
| Location | Contents | Commit? |
| /.agent/ | Episodic JSONL, semantic lessons, personal prefs | Yes (this is the shared memory) |
| /.agent/.dreamd/ | Local index, daemon state, config template, memory branches, provenance ledger | No (gitignored by init) |
| ~/.agent/registry.toml | Which projects have a store | No |
| ~/.agent/dreamd.sock | Daemon API socket (while running) | No |
npx -y dreamd-mcp setup (or dreamd setup after a cargo install) scaffolds the store by calling init, then writes the harness MCP config. init is the scaffold primitive and still works on its own when you want the store without touching any MCP config. Both are idempotent. To uninstall from a machine — stop local servers, remove the socket, unregister the current project, clear caches — run npx -y dreamd-mcp uninstall (project .agent/ stores are left in place). Advanced, registry-only: npx -y dreamd-mcp init --uninstall-project unregisters the current project and touches nothing else.
Drop a .agent/ folder in the project. Claude Code, Cursor, Cline, and other MCP-aware harnesses share it. What one agent learns, the next already knows. You can cat, grep, and git diff every byte. Durable appends go through MCP / the daemon so the writer stays single-writer.
This is not "another memory product." It is a storage-model wedge: the filesystem is the source of truth, and the MCP tools (searchnodes / appendnode) are a thin interface over those files.
Open core: Apache-2.0 core today, self-hosted only. Premium features may ship later. Do not read this as free-forever for everything.
bash
npx -y dreamd-mcp setup # scaffold .agent/ and wire your harness
npx -y dreamd-mcp # MCP server (stdio) — what the harness spawns
> First run prints a local-only privacy disclosure. setup prompts for harness choice when it has a TTY.
## The moment it earns its name
Recorded live, sped up 1.5x: Claude Code writes the lesson, OpenCode reads it back through the same .agent/ folder. Tape: docs/assets/demo.tape.
No re-explaining. No re-pasting. Same .agent/ folder, every harness.
## Install
### npm (recommended)
bash
npx -y dreamd-mcp setup # scaffold .agent/ + write the harness MCP config
npx -y dreamd-mcp # MCP server (stdio) — your harness spawns this
stdio stays the default transport. dreamd mcp --bind 127.0.0.1: is the opt-in Streamable HTTP server at /mcp. It is unauthenticated, and it is only in source builds with --features mcp-http — see docs/mcp-transports.md.
Requires a project root sentinel (.git/, Cargo.toml, package.json, or pyproject.toml).
setup prompts when it has a TTY. In scripts and non-interactive shells, pass --yes --harness claude|cursor|both (--harness none or --no-write-mcp scaffolds without touching any MCP config).
### Cargo / from source
bash
git clone https://github.com/botzrDev/dreamd.git
cd dreamd
cargo install --path crates/dreamd-cli
See CONTRIBUTING.md for the full dev setup.
## Quick start ( on the npm path, or cargo install --path crates/dreamd-cli if you want the dreamd binary. The shim forwards only some subcommands (npx -y dreamd-mcp --help lists them); recall, score, status, archive, and migrate need the dreamd binary.
Adapters: Claude Code · Cursor · Cline
## What dreamd writes
| Location | Contents | Commit? |
| /.agent/ | Episodic JSONL, semantic lessons, personal prefs | Yes (this is the shared memory) |
| /.agent/.dreamd/ | Local index, daemon state, config template, memory branches, provenance ledger | No (gitignored by init) |
| ~/.agent/registry.toml | Which projects have a store | No |
| ~/.agent/dreamd.sock | Daemon API socket (while running) | No |
npx -y dreamd-mcp setup (or dreamd setup after a cargo install) scaffolds the store by calling init, then writes the harness MCP config. init is the scaffold primitive and still works on its own when you want the store without touching any MCP config. Both are idempotent. To uninstall from a machine — stop local servers, remove the socket, unregister the current project, clear caches — run npx -y dreamd-mcp uninstall (project .agent/ stores are left in place). Advanced, registry-only: npx -y dreamd-mcp init --uninstall-project unregisters the current project and touches nothing else.
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/botzrdev-dreamd/)
- 来源
- github · https://github.com/botzrDev/dreamd
- 按领域浏览
- 记忆增强
- Traction
- 6 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。