N
nekyialabs/resonant-mind
Persistent cognitive infrastructure for AI systems
在 GitHub 查看 ↗链接已于 2026-11-14 核查 · HTTP 200 · 打开的是厂商自己的官网
官方说明Persistent cognitive infrastructure for AI systems. 28 MCP tools — semantic memory, emotional processing, identity continuity, and a subconscious daemon. Built on Cloudflare Workers.
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"nekyialabs-resonant-mind": {
"command": "npx",
"args": ["wrangler"]
}
}
}解析自我们于 2026-11-12 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"nekyialabs-resonant-mind": {
"command": "npx",
"args": ["wrangler"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio nekyialabs-resonant-mind -- npx wrangler
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 33 ★ · nekyialabs/resonant-mind · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-11-13 · 最近见到 2026-11-14 · 共见到 2 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 33 ★ · 1 个来源 · repo
- 安装
npx wrangler
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx wrangler。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: AI Agent。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
nekyialabs/resonant-mind；我们收录于 2026-11-13；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# Resonant Mind
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
A Postgres-backed cognitive substrate for persistent AI memory, identity, dreams, drives, relationships, and continuity.
Resonant Mind began as persistent memory infrastructure and was subsequently reshaped through use in long-running AI minds. Version 4 promotes that lived architecture into a generic single-mind public core.
## Status
The current release is v4.1.4. v4.0.0 was the Reshape release. The 4.1 releases add the v3.2 → v4 migrator and make entity merge lossless; see the changelog for each one.
Postgres-only at runtime: Neon through Cloudflare Hyperdrive
47 MCP tools organised by kinds of act
30-minute subconscious metabolism
R2-backed visual memory
pgvector semantic retrieval
Workers AI dream composition
no bundled dashboard or Observatory
no D1 runtime (D1 is supported only as a source for the v3.2 migrator)
no hard-coded person or household tenancy
> Upgrading from v3.2? Back up first. Before you run anything, take a full backup of your v3.2 database (and your images) and check that you can restore it. The User migration guide shows how for PostgreSQL and for D1.
> v3.2 → v4 migration (operator-assisted). Since 4.1.0 the migrate:v32 CLI moves a public v3.2 PostgreSQL or D1/SQLite mind into a fresh, separate v4 database. It never changes your v3.2 database, refuses anything it cannot prove instead of guessing, and checks the result column by column before it says you are ready to switch. Some steps stay yours: copying images, re-embedding with your provider, and switching your deployment over. Follow the User migration guide, or give your agent the Agent migration runbook. What has and has not been proven is in docs/migration-v32-v4-acceptance.md.
> A v3.2 D1 or SQLite mind that drifted from the public schema (a column added by hand, a table rebuilt, a dreams table of your own) is refused by inspect-source, as it should be. Since 4.1.4, normalise-source rebuilds a copy of it in the exact v3.2 schema and sets everything else aside for you to put back after the import. See "A source that has drifted from v3.2" in the user guide. A drifted PostgreSQL source has no such route yet.
> The v4 migration runner itself still sets up fresh v4 databases only; it deliberately refuses an existing v3 schema, so a v3 database is never upgraded in place.
> If your mind ever merged two entities on 4.1.1 or earlier, please read docs/merge-damage-check.md. A merge before 4.1.2 could leave orphaned or misfiled vectors and other traces behind. Upgrading stops new damage but does not repair old damage. npm run check:merge-damage is a read-only check, and npm run repair:merge-vectors clears the vector findings without destroying anything (it is a dry run unless given --apply). Every repair is the owner's decision.
## Architecture
The governing distinction is:
> Regions are kinds of act. Organs are kinds of state.
Regions include Ritual, Attention, Surgery, Compass, Spine, Bonds, Episodes, Active, Weather, Dreams, Drives, Inner Appetite, and Network.
The scheduled daemon metabolises memory rather than merely storing it: mood and affect, novelty and charge, retention, orphan detection, proposals, consolidation, reflection, dream recurrence, bond warmth, somatic markers, drives, redolence, identity proposals, and stale threads.
Resonant Mind began as persistent memory infrastructure and was subsequently reshaped through use in long-running AI minds. Version 4 promotes that lived architecture into a generic single-mind public core.
## Status
The current release is v4.1.4. v4.0.0 was the Reshape release. The 4.1 releases add the v3.2 → v4 migrator and make entity merge lossless; see the changelog for each one.
Postgres-only at runtime: Neon through Cloudflare Hyperdrive
47 MCP tools organised by kinds of act
30-minute subconscious metabolism
R2-backed visual memory
pgvector semantic retrieval
Workers AI dream composition
no bundled dashboard or Observatory
no D1 runtime (D1 is supported only as a source for the v3.2 migrator)
no hard-coded person or household tenancy
> Upgrading from v3.2? Back up first. Before you run anything, take a full backup of your v3.2 database (and your images) and check that you can restore it. The User migration guide shows how for PostgreSQL and for D1.
> v3.2 → v4 migration (operator-assisted). Since 4.1.0 the migrate:v32 CLI moves a public v3.2 PostgreSQL or D1/SQLite mind into a fresh, separate v4 database. It never changes your v3.2 database, refuses anything it cannot prove instead of guessing, and checks the result column by column before it says you are ready to switch. Some steps stay yours: copying images, re-embedding with your provider, and switching your deployment over. Follow the User migration guide, or give your agent the Agent migration runbook. What has and has not been proven is in docs/migration-v32-v4-acceptance.md.
> A v3.2 D1 or SQLite mind that drifted from the public schema (a column added by hand, a table rebuilt, a dreams table of your own) is refused by inspect-source, as it should be. Since 4.1.4, normalise-source rebuilds a copy of it in the exact v3.2 schema and sets everything else aside for you to put back after the import. See "A source that has drifted from v3.2" in the user guide. A drifted PostgreSQL source has no such route yet.
> The v4 migration runner itself still sets up fresh v4 databases only; it deliberately refuses an existing v3 schema, so a v3 database is never upgraded in place.
> If your mind ever merged two entities on 4.1.1 or earlier, please read docs/merge-damage-check.md. A merge before 4.1.2 could leave orphaned or misfiled vectors and other traces behind. Upgrading stops new damage but does not repair old damage. npm run check:merge-damage is a read-only check, and npm run repair:merge-vectors clears the vector findings without destroying anything (it is a dry run unless given --apply). Every repair is the owner's decision.
## Architecture
The governing distinction is:
> Regions are kinds of act. Organs are kinds of state.
Regions include Ritual, Attention, Surgery, Compass, Spine, Bonds, Episodes, Active, Weather, Dreams, Drives, Inner Appetite, and Network.
The scheduled daemon metabolises memory rather than merely storing it: mood and affect, novelty and charge, retention, orphan detection, proposals, consolidation, reflection, dream recurrence, bond warmth, somatic markers, drives, redolence, identity proposals, and stale threads.
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/nekyialabs-resonant-mind/)
- 来源
- github · https://github.com/nekyialabs/resonant-mind
- 按领域浏览
- AI Agent
- Traction
- 33 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。