Skip to content

docs: add a DeepSeek Harness overlay example - #34

Merged
DottytheHomeless merged 1 commit into
mainfrom
docs/dsh-integration
Aug 20, 2026
Merged

docs: add a DeepSeek Harness overlay example#34
DottytheHomeless merged 1 commit into
mainfrom
docs/dsh-integration

Conversation

@MXAntian

Copy link
Copy Markdown
Contributor

Why there is no plugin here

dsh ships no memory layer of its own, and its design notes reject per-provider plugins outright:

Rejected because it repeats auth, configuration, lifecycle, and tool wrappers that MCP already standardizes and expands ownership for every added provider.

The supported path is a Cordis overlay pointing their generic @deepseek-ai/dsh-mcp-client at whatever server you want. mneme already speaks stdio MCP — which is the only thing that overlay requires — so the integration is a config file and nothing else.

Added here rather than upstream because dsh does not accept external pull requests ("We are sorry that we cannot accept external pull requests at the moment").

What's in it

examples/dsh.cordis.yml, structured to mirror their own examples/mcp-memory overlays. One deviation: command: node plus an absolute script path instead of a bare executable, because mneme is not on npm with a bin and there is nothing on PATH to invoke.

The comments carry the two failure modes a new user actually hits, both silent:

no TOKENMEM_DB_PATH DB resolves against the process working directory — the store built in one session can be invisible from the next
no EMBEDDING_API_* starts and answers fine, as FTS5 keyword search only. Hybrid recall is the reason to run mneme; losing it is not an error, just a quieter and worse result set

Honesty about coverage

README lists this under "Config provided, not verified by us", not in the "Tested with" table. CI here exercises mneme's own MCP server, not dsh's loader — and claiming otherwise, in the same document that warns about silent degradation, would be its own small version of that sin.

Docs + one example file. No code paths touched.

🤖 Generated with Claude Code

dsh ships no memory layer, and its design notes reject per-provider plugins
outright — "it repeats auth, configuration, lifecycle, and tool wrappers that
MCP already standardizes and expands ownership for every added provider". The
supported path is a Cordis overlay aiming their generic MCP client at whatever
server you want.

So there is nothing to build. mneme already speaks stdio MCP, which is the only
thing that overlay requires; the integration is a config file. Adding it here
rather than upstream because dsh does not accept external pull requests.

Structure mirrors their examples/mcp-memory overlays, with one deviation worth
naming: `command: node` plus an absolute script path instead of a bare
executable, because mneme is not published to npm with a `bin` and there is
nothing on PATH to invoke.

The comments carry the two failure modes a new user actually hits, both of
which are silent rather than loud:

  - no TOKENMEM_DB_PATH -> DB resolves against the process working directory,
    so the store built in one session can be invisible from the next
  - no EMBEDDING_API_* -> starts and answers fine, as FTS5 keyword search only.
    Hybrid recall is the reason to run mneme; its absence is not an error, just
    a quieter and worse result set

README lists it under "Config provided, not verified by us" rather than in the
"Tested with" table. The CI here exercises mneme's own MCP server, not dsh's
loader, and claiming otherwise in the same document that warns about silent
degradation would be its own small version of the same sin.
@MXAntian
MXAntian marked this pull request as ready for review August 20, 2026 05:56
@DottytheHomeless
DottytheHomeless merged commit 603337d into main Aug 20, 2026
2 checks passed
@DottytheHomeless
DottytheHomeless deleted the docs/dsh-integration branch August 20, 2026 06:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants