dsh-mem0-plugins

English | 简体中文

Persistent memory for the DeepSeek Harness (dsh) web profile, backed by a
self-hosted Mem0 server. The plugin gives your
agent long-term memory with zero manual effort: relevant memories are recalled
before answering, and every finished conversation turn is distilled into facts
and written back automatically.

[!IMPORTANT]
Compatibility — read this first. This plugin speaks the custom HTTP API of
runfali/mem0-graph
(X-API-Key auth, POST /search, POST/PUT/DELETE /memories,
POST /evolve/feedback) and works only against a server deployed from that
project. It does not support Mem0 Cloud or the official mem0 OSS REST/SDK
API, and it is not a drop-in for other Mem0 deployments.

It ships as a standard dsh bundle plugin: dsh plugin add to install,
dsh plugin remove to uninstall. It changes no dsh source code.

Table of Contents

• What it does automatically
• Model tools
• Requirements
• Installation
• Configuration
  • Connection & identity
  • Automatic recall & query distillation
  • Automatic write-back (tidal coalescing)
  • Reliability & timeouts
• Recall design
• Reliability design
• Observability
• Development & testing
• Troubleshooting
• Documentation
• License

What it does automatically

Interrupted turns are never written: a half-streamed reply is not a durable
conversation truth.

Model tools

Four tools are registered under the dsh agent:

Requirements

• Node.js ≥ 22 and a working DeepSeek Harness install
  (web profile).
• A running runfali/mem0-graph
  server reachable over HTTP (e.g. http://127.0.0.1:8888).
• If the server runs with auth enabled, an API key created from its dashboard.
  With AUTH_DISABLED=true, leave the key empty.

Installation

# Install into the web profile (restart dsh afterwards)
dsh plugin --profile web add /path/to/dsh-mem0-plugins

# Uninstall
dsh plugin --profile web remove dsh-mem0-plugins

The plugin is enabled by default and needs zero configuration when pointed
at a local AUTH_DISABLED server. Changes made in the settings page take effect
immediately — no restart needed. To turn memory off entirely, flip Enable
plugin off in the settings card; the card header always shows the current
enabled state and host at a glance.

Configuration

All settings live in the dsh settings page under the mem0 namespace. Values
saved there override profile-layer defaults.

Connection & identity

Automatic recall & query distillation

Automatic write-back (tidal coalescing)

Reliability & timeouts

To change profile-layer defaults (applies to all users of the machine), append
to ~/.dsh/profiles/web/cordis.patch.yml:

- id: mem0
  config:
    enabled: true
    host: http://mem0.internal:8888
    apiKey: your-admin-api-key

Recall design

• Explicit tool pipeline. No silent background prefetch — the dsh platform
  has no content-injection hook after message echo (see
  docs/COMPARISON.md for the platform timing analysis).
  The model calls mem0_search following usage guidance; the tool card shows
  the recall happening, and distillation / hedging / the breaker all run inside
  the tool.
• Forced recall step (default on). Every turn's first step gets a
  plugin-source notice ("answer only after calling mem0_search") rendered as a
  collapsed context-injection line in the UI. It never writes memory, skips
  trivial turns, and can be turned off with forceRecallStep.
• Trivial-input guard (src/guards.js). Pure greetings,
  confirmations, and slash commands are classified by exact whole-string match
  against word lists — a real sentence is never misclassified. The same word
  list backs an explicit exemption written into both the usage section and the
  mem0_search description: when the ENTIRE message is a bare
  acknowledgement/continuation (好的、嗯、收到、继续、ok…), the search is
  skipped; any actual content restores the mandatory search.
• Query distillation. Ported from hermes
  agent/memory_manager.py::_distill_query, applied to the recall query only
  (never the write path):
  1. Query ≤ distillMinChars: search as-is;
  2. Long queries (pasted logs/code): truncate to distillInputMaxChars, ask a
     small model for a 2–4 keyword retrieval intent, then search with that;
  3. Language-drift guard: distilled output of Chinese input containing
     Vietnamese diacritics or other non-Latin/non-CJK characters (an observed
     small-model routing failure) is treated as pollution and rejected;
  4. Hedged requests: a silent first request triggers one concurrent retry;
  5. Total failure: fall back to the raw query — retrieval never silently dies.

Reliability design

• Circuit breaker: breakerThreshold consecutive failures pause all mem0
  traffic; auto half-open after breakerCooldownMs. HTTP 404 / not-found style
  client errors don't count toward the breaker.
• Connection-level retry: connection-refused/DNS failures retry once — the
  request most likely never reached the server, so no duplicate writes.
• Bounded queue: pending writes capped at queueMaxLen (oldest dropped) so
  a long server outage can't grow memory unbounded.
• Flush-on-dispose: all open coalescing buckets are flushed when the plugin
  stops — queued memories are never lost.

Observability

Coalescing and write-path hygiene counters go to the dsh host process logs
(not the browser): the plugin logs through both ctx.logger (internal) and
console.log/warn (host stdout). With systemd: journalctl -u dsh.service -f;
otherwise watch the dsh process stdout.

Every merged flush logs one info line with cumulative totals:

[dsh-mem0] mem0 coalesced 3 turn(s) into 1 write (session=<id>, saved 2 call(s), chars=512, trigger=idle; totals: batches=12 savedCalls=34 dropped=0 jsonSanitized=3)

Queue drops log a warn; JSON stripping and fast-path writes are debug-level;
breaker transitions and failed direct writes always warn.

Development & testing

git clone <this-repo> && cd dsh-mem0-plugins
npm install                # or symlink your dsh node_modules for offline dev
node test/smoke.mjs        # host half: apply pipeline + tools + write path + guards
node test/client-smoke.mjs # client half: bundle load + locale/slots + settings form save

Troubleshooting

Documentation

• docs/COMPARISON.md — design notes vs. the hermes
  original, including the platform timing constraints that shaped the
  tool-driven recall (Chinese).

License

MIT © 2026 dsh-mem0 contributors