DSH Marketplace

dsh-mnemon

omdsh-dev/dsh-mnemon

Cross-agent, local-first persistent memory plugin for DeepSeek Harness (DSH), powered by Mnemon. It shares long-term memory across Mnemon-enabled agents and adds runtime memory, searchable project documents, semantic recall, knowledge graph, and a Sidebar UI.

754TypeScriptMITSource

Install

Add dsh-mnemon to DeepSeek Harness

via npm

Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.

via GitHub · npm package

Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.

What happened when we ran it

Installed cleanly when we ran it

Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run yesterday.

Due diligence

Before you install dsh-mnemon

  • Source of record: omdsh-dev/dsh-mnemon — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.
  • Detected: terminal surface. Read the source before granting these.
  • A listing here is not a security review. Plugins run with your agent's permissions.

The AI take

What it is — DeepSeek Harness plugin integrating Mnemon for persistent memory and cross-agent sharing.

Who it is for — When using DeepSeek Harness for multi-turn document-heavy tasks, people who need persistent context are suitable to install this plugin. When a task only relies on real-time tool results without needing historical memory, it does not need to install this plugin.

Watch out — Sandbox test passed in a fresh profile. Static check indicates execution of shell commands. No obvious pitfalls found.

The verdict — I would install it because the sandbox test passed providing persistent memory support, but the premise is first installing Mnemon, and only worth when cross-agent sharing is needed.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

What dsh-mnemon does

Three memory layers route compact context, documents, and linked facts into a shared reservoir.

dsh-mnemon is a DeepSeek Harness plugin that adds local-first, persistent memory shared across Mnemon-enabled agents. It separates information into Runtime Memory, Project Documents, and Memory Spaces rather than copying everything into one store. Runtime preferences, collaboration rules, project conventions, and environment facts are projected as compact USER.md / MEMORY.md context on each turn. Documents remain complete Markdown references that can be searched before being loaded. Memory Spaces provide bounded recall for cross-session facts, decisions, entities, and relationships.

The deterministic dsh-mnemon Host handles storage, workspace and interaction rules. Search performs provider-native, read-only recall; Agent Query gives a clean task Agent bounded evidence; Remember and Save to memory ask a task Agent to qualify, route, deduplicate and distil accepted writes. The native Mnemon engine uses its local CLI and SQLite. Other supported providers include OpenViking, Honcho, Mem0, Hindsight, Holographic, RetainDB, ByteRover and Supermemory. Settings → Memory System → Background task Agent selects the provider and model for background tasks.

This suits agents that need durable, searchable context across sessions or shared long-term memory. It is a poor fit where transient conversation context is sufficient, or where adding a separate memory service is undesirable. Mnemon must be installed separately, and the README requires Node.js 20 or newer. The terminal surface is relevant because local providers can be reached through CLI programs, including Mnemon and ByteRover, with the agent operating under its available permissions.

dsh-mnemon documentation

How it behaves

The plugin exposes three non-interchangeable tiers:

Tier Content Access
Runtime Preferences, rules, conventions and environment facts Compact USER.md / MEMORY.md projection on every turn
Documents Designs, investigations, procedures, postmortems and handoffs Search first, then full Markdown on demand
Memory Spaces Cross-session facts, decisions, entities and relations Bounded recall from active spaces

Current instructions, repository files and live tool results take priority over historical memory. Background tasks use DSH’s new-session model route by default and do not reuse or consume the main conversation history.

Actions

The WebUI actions are deliberately separated by data effect:

  • Search performs concurrent, provider-native read-only recall.
  • Agent query starts a clean top-level task Agent with bounded evidence and returns an answer without writing memory.
  • Remember and Save to memory let a task Agent qualify, route, deduplicate and distil a candidate; the Host writes only accepted results.
  • Smart selection applies hard provider rules and asks a task Agent to resolve genuine ambiguity, then saves a routing receipt.
  • AI metadata creates local titles and descriptions asynchronously for selected Memory Spaces.
  • Archive Document creates a searchable cold reference before the Host moves the original.
  • Turn memory expands exact recall, write and Document-search activity, with navigation to each source.

Providers

Mnemon is the official prioritised native engine, using a local CLI and SQLite. Optional providers are OpenViking, Honcho, Mem0, Hindsight, Holographic, RetainDB, ByteRover and Supermemory. External providers are off by default. Provider capability differences remain visible; the plugin does not invent graph edges, deletion semantics or enumerable content.

Configuration and requirements

Reusable Provider services are managed in Settings; concrete Memory Space instances, activation, scope and metadata are managed in Memory Spaces. Settings → Memory System → Background task Agent selects a dedicated Provider and model for background tasks. The README requires Node.js 20 or newer and a separately installed Mnemon. macOS and Linux installation paths use Homebrew or Go; Windows uses the official v0.2.3-or-newer release ZIP.

Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub

Same category

Alternatives to dsh-mnemon

29k

OpenViking memory and context bundle for DeepSeek Harness: pre-step auto-recall and profile injection, session capture, `viking://` URI guarding, and recall/write memory tools backed by an OpenViking server.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourcePythonyesterday

AI review

dsh-memory-plugin

What it is — Integrates OpenViking memory and context bundle into DeepSeek Harness.

Who it is for — When using DeepSeek Harness for multi-turn agent tasks that require persisting context and profile injection, this plugin is suitable. If your work does not involve viking:// URI management, then this plugin is not applicable.

Watch out — May execute shell commands. Not tested in sandbox. No obvious issues found.

The verdict — I would install it because it allows agents to operate on context like a file system.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details

coding-agents

vectorize-io

20k

Hindsight, agent memory that learns: long-term project memory with auto recall and retain, knowledge pages, deep reflection, and per-repo memory banks.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourcePythonyesterday

AI review

coding-agents

What it is — Hindsight provides long-term project memory management for coding agents.

Who it is for — Developers using AI coding assistants such as Claude Code for code development should install it. If you use a non-Python language for the agent, you can choose other implementations.

Watch out — The plugin requires an API key or token and will execute shell commands. Sandbox testing has not been performed. No obvious pitfalls found.

The verdict — Without sandbox testing results, I would not install it.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
2Details

dsh-context

bowenliang123

185

Context insight panel: see what the model's context window is made of and how it evolves — composition vs. window size, per-request history, compression/injection events, and per-message token stats.

Installed cleanly when we ran it

npm packageTypeScriptyesterday

AI review

dsh-context

What it is — dsh-context is a DeepSeek Harness plugin for context insight.

Who it is for — If you use DeepSeek Harness for multi-turn conversations, you should install it. If you use a small context window model, you can skip it.

Watch out — Sandbox testing confirmed successful registration in a new profile. No obvious issues found.

The verdict — I would install it because it shows context evolution details that matter in conversation management.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Details
158

为 DeepSeek Harness 带来「跨会话长期记忆 + 后台自我进化」能力的纯插件实现:五轨记忆 · git 分支感知 · 回合内自我审查 · 技能自我进化与技能管理器 · 四轨待办 · COI 调度 · 会话广播 · 会话搜索 · 提示词管理器 · 临时信息便签——零核心修改、零运行时依赖,随装随用、卸载即净。

Installed cleanly when we ran it

GitHub sourceJavaScript2d ago

AI review

dsh-memory-evolve

What it is — dsh-memory-evolve brings cross-session long-term memory and background self-evolution capabilities to DeepSeek Harness.

Who it is for — Developers maintaining multiple projects in parallel can use it to maintain context consistency via five-track memory, four-track todos, and local file search. Users who only work on single-session tasks do not need cross-device memory synchronization or external agent delegation.

Watch out — Sandbox testing passed after installation in a new profile, where it was registered by DeepSeek Harness. Static analysis shows the plugin will execute shell commands. No obvious issues found.

The verdict — I would install it because it supports collaboration between internal AI sessions and external agents through memory and session rooms, but only if the main session's DSH process remains running.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

engramory

tinqiao-oss

155

The Engramory curated-memory discipline as an installable plugin ([npm: dsh-engramory](https://www.npmjs.com/package/dsh-engramory)): a deterministic 200-line / 25 KB cap on the `MEMORY.md` index via `ctx.tools.guard()` — growth denied, a shrinking rewrite always passes — plus the protocol registered as a runtime skill. The store is plain markdown, one file per fact, shared with Claude Code, Codex, Kiro, and OpenClaw.

Installed cleanly when we ran it

GitHub sourcePythonyesterday

AI review

engramory

What it is — DeepSeek Harness plugin providing Markdown memory curation protocol with 200-line/25KB index cap.

Who it is for — When you need a local file-based memory curation, this plugin fits your scenario. If your work requires relevance-loaded skill or database memory, this is not suitable.

Watch out — Installation from source requires providing API key or token and executing shell commands. Sandbox test passed: registers in a new profile by harness. No obvious pitfalls found.

The verdict — I would install it because it offers a PreToolUse hook denying growth past the cap.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
2Details

dsh-noema

ZSeven-W

100

Noema long-term memory plugin for DSH: durable, inspectable agent memory with recall tools and a settings page.

Installed cleanly when we ran it

npm packageTypeScript4d ago

AI review

dsh-noema

What it is — The dsh-noema plugin provides durable, inspectable agent memory for DeepSeek Harness by integrating with Noema and including recall tools and a settings page.

Who it is for — It suits users developing cross-session agents with DeepSeek Harness who need persistent knowledge retention. Users relying solely on short-term sessions do not need it.

Watch out — The plugin executes shell commands. Sandbox testing passed after installation in a fresh profile and registration with harness. No obvious issues found.

The verdict — I would install it if cross-session memory retention is required, because it enables importing memories from other tools and managing storage via the settings page.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source