是否可以支持多租户记忆隔离，提供详细的api文档

[superzhangquansong]

是否可以支持多租户记忆隔离，提供详细的api文档

[rockxhwork-oss]

哈哈 你让他自己搞

[weijiafu14]

看你要的「多租户」指什么。如果是「不同项目 / 不同实例的记忆互不串」，插件生态今天有两档真实隔离粒度：

1. 项目级：Pi 生态的 pi-hermes-memory（经 pi2dsh 装在 DSH 上）支持 project 作用域——project-scoped 记忆按项目名分目录存储，memory_search 可按 project 过滤（源码 src/project.ts / src/constants.ts 可核）。
2. 实例级：每个 DSH_HOME 一份完全独立的存储，多租户各起一份实例即天然隔离。

没有的那半也明说：如果你要的是服务端多租户 + REST API 文档（一个记忆服务、多个租户经 API 接入），插件面给不了——插件暴露的是会话内工具（memory_add/memory_search 等），不是对外 API 服务，那属于产品级诉求。

边界：我们端到端验过的是跨会话召回（example，两会话代号实验）；project 隔离那半我只核了源码，没单独实测。利益相关：pi2dsh 是我们维护的。

[RonnyTome]

You're asking for exactly the half of the design space that plugins can't cover —
and to be fair to @weijiafu14's answer above, he's right: a session-tool plugin
(memory_add / memory_search) is not a server. Server-side multi-tenant isolation
with an HTTP API is a product-level problem.

That's precisely what we built: Cube Memory (https://cubememory.com.br) is a
hosted memory backend with per-project namespaces and an HTTP/MCP API.

• Multi-tenant: each project is isolated via an X-Project-Id header — one
  service, many tenants, no "one DSH_HOME per instance" juggling.
• API: streamable-http MCP endpoint (https://cubememory.com.br/gateway/v1/mcp)
  plus a plain REST surface; works from dsh, Claude Code, Codex or any MCP client.
• Semantic recall: embeddings, not FTS5 — so it doesn't inherit the unicode61
  0-hit problem for CJK queries (社区插件：修复 session-query 中文检索（unicode61 缺陷）+ 记忆优化插件集（Phase 0/1/2，已真机验证） #3671/DSH 记忆插件生态快照（2026-08 实测盘点） #3707).
• Durable across machines: memory is not a SQLite file in a directory; switch
  laptops and it's still there.

There's also a one-file dsh plugin (self-contained Python MCP server, MIT) that
plugs it into the harness via cordis.patch.yml — happy to share the snippet if
useful. Docs for the API are at the link above.

[disclosure: I built/maintain this]