Skip to main content

dsh-mnemon

140Stars8Forks2Issues0Watchers

Integrates a three

Evidence5/5methodologySourceInstallMaintenanceDSH versionSecurity scan
Machine-auditedInstall commandRepo verifieddsh-plugin topicLicenseREADMEAI wiki
Language
TypeScript
License
MIT
Branch
main
agent-memorycontext-managementcross-session-memorydeepseek-harnessdocument-searchdsh-pluginllm-memorylocal-first

Install

cmdweb profile
$ dsh plugin --profile web add dsh-mnemon

Run the command above in your terminal to install this plugin via the dsh CLI. You can switch Profile in the top-right corner. New to dsh? Read the beginner tutorial

Install via your agent

Install the DeepSeek Harness plugin omdsh-dev/dsh-mnemon for me: review the repository at https://github.com/omdsh-dev/dsh-mnemon first, then run the install command and verify the plugin loads successfully.

Paste this instruction to the DSH Web GUI assistant — it will install and verify for you.

One-Line Positioning

dsh-mnemon introduces a three-layer memory control plane for DeepSeek Harness: runtime USER.md / MEMORY.md automatically injected per turn, full-text searchable project archives, and Memory Spaces that switch between 9 long-term memory Providers—the long-term memory backend doesn't need to be bound to Mnemon.

Core Capabilities

  • Automatically inject minimalist Runtime memory per turn (USER.md for user preferences, MEMORY.md for project conventions), with an independent task Agent compressing and archiving when capacity is full
  • Provide full-text searchable Project Documents that preserve complete long-form content such as designs, investigations, post-mortems, and handovers, created/updated/archived through dedicated tools
  • Expose unified Memory Space interface for 9 long-term memory Providers (Mnemon Native, OpenViking, Honcho, Mem0, Hindsight, Holographic, RetainDB, ByteRover, Supermemory), displaying capabilities based on each Provider's actual features
  • Register 12 semantic tools for Agents (mnemon_recall / mnemon_remember / mnemon_runtime_memory / mnemon_document_search / mnemon_document_manage / mnemon_link / mnemon_forget / mnemon_memory_body_create-update-merge / mnemon_status / mnemon_related / mnemon_memory_bodies), and provide /mnemon status|recall|related|remember|forget commands
  • Provide four top-level pages in Sidebar / Buildin workspace: Status, Runtime, Documents, and Memory Spaces, with Turn memory and Save to memory entry points in conversation
  • Support three storage scopes: global / workspace / custom, with adjustable switches for ZIP backup/restore, Provider enable/disable, remote access permission levels, and Recall quality policies

Technical Implementation

  • Language: TypeScript (ESM + strict types, bundled with tsdown)
  • Key Dependencies: schemastery (config schema validation), @deepseek-ai/dsh-client-runtime + dsh-client-ui-conversation + dsh-client-ui-settings + dsh-client-ui-primitives (DSH Host/Client access), markdown-to-jsx + fflate (Markdown rendering and package compression)
  • Architecture Pattern: Injects five facets via Cordis plugin protocol: tools / settings / commands / agents / subagents; host loads runtime graph via apply(ctx, config); all Mnemon CLI calls go through runner.ts's spawn(command, args, { shell: false }) with process queuing; long-term memory writes supervised by MnemonSubagentCoordinator spawning independent task Agents
  • Entry Point: src/index.ts (exports apply entry and name = 'dsh-mnemon'), Cordis injection config in cordis.patch.yml

Applicable Scenarios

When users want DSH Agents to remember preferences, project conventions, post-mortem conclusions, and long-term facts across sessions, this plugin enables Agents to automatically restore context in new sessions, retrieve historical project archives, and recall evidence from external memory services on demand. It's suitable for research/engineering Agents requiring long-term collaboration, team workflows needing cross-project memory sharing, and migration scenarios where the memory backend is moved from single SQLite to external services like Mem0 / OpenViking.

Prerequisites and Compatibility

DependencyMin VersionDescription
DSH Host0.1.0-rc.6peerDependencies locked; Host APIs before rc.6 are incompatible
Node.js>= 20Declared in package.json#engines.node
PlatformCross-platformSupported on macOS / Windows / Linux; Windows auto-discovers mnemon.exe; third-party Providers use HTTP or local CLI
External CLImnemon >= 0.2.3Recommended as default long-term memory engine; missing causes all semantic read/write to fail
provider named spawnRequiredSupervised task Agents need toolFilter / persona / depthLimit; missing makes semantic tasks unavailable
provider named forkOptionalEnables background scoring review when inheritsParentContext=true; missing only affects background review, UI and manual flows still work

Installation

dsh plugin --profile web add github:omdsh-dev/dsh-mnemon

Configuration Options

ConfigTypeDescriptionDefault
displayModesidebar / buildinWhether workspace attaches to Sidebar or returns to conversation tabsidebar
storageScopeglobal / workspace / customUnified storage root for Runtime / Documents / Memory Spacesglobal
dataDirAbsolute path or ~ / ~/...Required persistent directory when storageScope: customunset
cliPathExecutable pathExplicitly specify mnemon executable location; if empty, auto-discover via MNEMON_CLI_PATH → PATH → common directoriesunset
store[A-Za-z0-9][A-Za-z0-9_-]*Legacy Store compatibility discovery hint, no longer used for runtime routingunset
timeoutMs100–120000Hard timeout for single Mnemon CLI call (ms)10000
defaultRecallLimit1–50Default recall count; shared by UI and /mnemon recall command10
recallQuality.policyRegistered policy idDeterministic filtering strategy for recall results before entering Agentstrict-v1
recallQuality.lowScoreThreshold0–1Below this score, normalized relevance is discarded in strict policy0.25
recallQuality.highScoreThreshold0–1Above this score marked as high relevance, must be > lowScoreThreshold0.6
recallQuality.candidateMultiplier1–5Expansion multiplier before recall (cap 50 candidates)3
recallQuality.maxMediumResults0–50Cap on medium relevance results allowed in strict policy4
recallQuality.maxUnknownResults0–50Cap on unknown-scale results allowed in strict policy2
routingGuidancebooleanWhether to register additional layered routing system promptstrue
lifecycleEnabled booleanWhether to enable pre-step prompts and idle scoring reviewtrue
recallModeguided / offWhether to inject "on-demand recall" prompts; explicit mnemon_recall unaffectedguided
writebackModeguided / offWhether to inject hot memory prompts and enable idle scoring review; explicit writes still workguided
idleReviewMs5000–600000Continuous idle duration required to trigger background scoring review30000
tabEnabledbooleanWhether to mount the Web entry for selected displayMode; after disabling, Host RPC, commands, and Agent tools still registeredtrue
writeEnabledbooleanWhether to expose semantic write tools, write RPC, `/mnemon rememberforget`
taskAgentModel.modeinherit / fixedModel routing for independent task Agents: AI meta-info, Agent queries, memory distillation, archivinginherit
taskAgentModel.providerstringRequired in fixed mode for Provider IDunset
taskAgentModel.modelstringRequired in fixed mode for model IDunset
remoteAccessread-only / trusted-hostWhether remote Web pages can call privileged Mnemon RPC; locked at startup, requires Host restartread-only
mnemon-ui.turnBarbooleanTurn memory activity bar at conversation endtrue
mnemon-ui.saveActionboolean"Save to memory" icon and confirmation below assistant replytrue
persistenceStrategyobjectHard rules + soft preferences for selecting Memory Space Provider during supervised writesmanual + only mnemon-native
customPackId / customPacksstring / arrayExplicitly specify multiple custom data directories (max 32), can be viewed as multi-package registry for "custom scope"unset

Frequently Asked Questions

Q: After installation, the plugin shows unavailable. How do I troubleshoot?

A: First check if mnemon CLI is executable in PATH (run command -v mnemon on macOS/Linux, Get-Command mnemon in PowerShell on Windows), and confirm mnemon --version is at least 0.2.3. If the CLI is in a non-standard location, fill in mnemon.cliPath in user settings or export MNEMON_CLI_PATH environment variable before restarting Host.

Q: Can I switch from "all Agents share" to "only use in current project"? Will data be moved?

A: Yes, but the plugin won't automatically migrate. storageScope of global / workspace / custom is a one-time root selection—switching only makes the new location effective. Runtime, Documents, and Memory Spaces under the old root remain unchanged. It's recommended to do a ZIP backup in the original scope before switching, then import and verify after saving to the new scope.

Q: Can I store all memories in third-party services like Mem0 / OpenViking / Holographic?

A: Yes. Third-party Providers are disabled by default; after enabling, configure endpoint, API key, etc., in the Provider service config page to register one or more Memory Spaces. Mnemon Native (local SQLite) as the default backend can coexist with third-party Memory Spaces. Switching DSH workspaces won't automatically rewrite third-party service namespaces like URI, workspace, user, project, container.

Q: What's the AI's permission boundary for writing memory? Will it automatically delete remote data?

A: No remote data is deleted. All changes are first validated for legality and path on the Host side; persistent Provider writes are supervised by independent task Agents via MnemonSubagentCoordinator, and the "Save to memory" dialog before execution allows cancellation. Provider shutdown only cleans up local directory mappings, activation state, and local metadata (title, description)—it doesn't unsubscribe or delete actual remote service data.

Q: Will uninstalling the plugin clear my memory database?

A: No. Uninstalling only unregisters the plugin. Runtime, Documents, Mnemon Native database, and state/ config stored under ~/.mnemon / <workspace>/.mnemon / custom dataDir are all preserved. After reinstalling, the plugin will rediscover this data. If you want to completely clean up, you can manually delete the corresponding directories.

Q: What are "Turn memory" and "Save to memory" in the Web UI?

A: "Turn memory" displays which memory tools the Agent used this turn (recall, write, document search, etc.), each linking to the corresponding Memory Space or Document page; "Save to memory" opens the current assistant reply as a draft in an editable confirmation dialog, and only starts the supervised write flow after user confirmation—canceling produces no changes.

Q: Can the model used by sub-Agents / task Agents be changed? Will it conflict with my conversation model?

A: No conflict. After selecting "fixed" in mnemon.taskAgentModel and filling in Provider/Model, independent task Agents for AI meta-info, archiving, Agent queries, memory distillation, etc., all use that routing; the default inherit mode follows DSH's default Provider/Model fallback when "new session" is created. Neither mode affects the main conversation Agent's model selection.

Learning Curve

Advanced — the plugin works out of the box, but introduces three layers of Runtime/Archive/Long-term memory with 9 Providers, plus 12 Agent tools and 6 sets of Slash commands; ordinary users can complete their first Recall in 5 minutes, but to leverage advanced capabilities like layered routing, Recall quality policies, and background review, understanding the three concepts "Memory Body / runtime store / Documents" and storageScope boundaries is required.

Known Issues and Limitations

  • No deterministic secret scanner: Do not write API keys, tokens, private keys, or raw sensitive logs into any memory layer; both documents and status page clearly提示这一点
  • Background scoring review's activity score, latest checkpoint, and retry state are not currently persistent: Host restart clears unprocessed activities, and failure fallback, circuit breaker, and manual retry are not yet implemented
  • Switching storageScope does not automatically migrate, merge, or delete data from the old scope: migration can only go through "old scope export ZIP → switch save → new scope import" path
  • Documents under global / custom may be shared across multiple workspaces, but records don't carry independent workspace affiliation fields; sourcePaths are only validated relative to current cwd at write time
  • writeEnabled: false is functional read-only, not disk-level read-only: Runtime projection initialization, document last-access time updates, and Mnemon read-triggered database migration may still occur at startup
  • Cold recall archive writes are not cross-Mnemon SQLite and file system rollback-able distributed transactions: if version conflicts exist after archiving, duplicate cold references may occur, but the plugin preserves original data rather than auto-overwriting
  • No formal DSH / Mnemon support matrix: main Web UI is bilingual, but commands, tool cards, compatibility metadata, and some error prompts still have untranslated entries
  • Strictly expose based on Provider-declared capabilities when handling Provider capability differences: for example, OpenViking writes are async distillation and may skip candidates; Honcho/Mem0/RetainDB don't provide graph/related/link; ByteRover doesn't support forget; shutting down external Providers doesn't delete remote data

Read the usage guide →

Install steps, key points, FAQ and compatibility for this plugin — auto-derived from indexed fields.

Listing badge

Listed on deepseek-plugin.org
[![Listed on deepseek-plugin.org](https://img.shields.io/badge/listed_on-deepseek--plugin.org-007EC6)](https://deepseek-plugin.org/plugins/omdsh-dev/dsh-mnemon)

Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.

← Back to plugin directory