Mnemon
中文
mnemondsh-mnemon
Contents

v0.2.0: A Pluggable Three-tier Memory System

View source on GitHub

v0.2.0 evolves dsh-mnemon from a Mnemon workbench into a long-term-memory Provider control plane. Runtime Memory and Project Documents remain reliably managed by dsh-mnemon, while third-tier Memory Spaces can now use Mnemon, OpenViking, Honcho, Mem0, Hindsight, Holographic, RetainDB, ByteRover, or Supermemory.

What changed

  • Nine Providers share one workflow for service settings, Memory Space instances, activation, recall, content, entities, distillation, and health observation.
  • Providers are off by default. Settings owns services; Memory Spaces owns instances.
  • New spaces can use an explicit Provider or rule + prompt driven smart selection.
  • AI metadata, Agent query, Remember, and Document archive use clean independent top-level task Agents.
  • Background task Agents can follow the DSH new-session model or use an explicitly selected Provider and model.
  • Memory Spaces perform one full synchronization on first entry and reconnect individual spaces on demand instead of blocking on a 15-second poll.
  • Status, Memory Spaces, content, and recall load concurrently and progressively; a local failure no longer blocks the whole page.
  • The default Sidebar order is now Status, Runtime, Documents, Memory Spaces.
  • Global, workspace, and custom scope now extend to local Providers that support those semantics while remote Providers retain their native namespaces.
  • Turn memory and Save to memory preserve the established conversation mental model and navigate precisely into the new multi-Provider surfaces.

Upgrading from 0.1.x

  1. Back up the current Mnemon root or export a Mnemon Pack from Settings.
  2. Update dsh-mnemon and restart the affected DSH profile.
  3. Open Settings → Memory System and verify presentation, storage, and background task-Agent model routing.
  4. Enable and save external Provider services one at a time when needed; every external Provider remains off by default.
  5. Open Memory Spaces → Overview for first discovery and synchronization, then inspect instance scope and activation.
  6. Verify one raw search and one Agent query before writing or migrating data.

The upgrade never migrates, merges, or deletes ~/.mnemon, workspace .mnemon, custom roots, or remote Provider data automatically. Disabling an external Provider clears only dsh-mnemon's local catalog metadata; reconnecting rebuilds it from the Provider.

  • Node.js 20 or newer;
  • DeepSeek Harness 0.1.0-rc.6;
  • Mnemon 0.2.3 or newer when using Mnemon Native.

See the capability map for the complete operation surface, long-term memory providers for fields and deployment requirements, and operations for backup and troubleshooting.