DSH Marketplace

dsh-mneme

modusensus/dsh-mneme

The memory that dreams — cross-session memory for DeepSeek Harness: recalls you across sessions, auto-consolidates in its sleep (autoDream), freezes conflicting memories for your review, and keeps a replayable audit trail. Offline-first local semantic search over SQLite with human-editable Markdown mirrors, an entity graph, an interactive memory panel, plus an external API and CLI.

23425JavaScriptMITSource

Install

Add dsh-mneme to DeepSeek Harness

Install into

via GitHub · GitHub source

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 11d agoon DeepSeek Harness 0.2.2-rc.1.

Show it in your README

install verified — dshmarketplace

For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.

Due diligence

Before you install dsh-mneme

  • Source of record: modusensus/dsh-mneme — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.

Security

What installing dsh-mneme runs

Build scripts

No build script was blocked in our run.

Source: our sandbox install on DeepSeek Harness 0.2.2-rc.1, 11d ago.

Install hooks

package.json declares no preinstall, install or postinstall script.

Source: package.json on GitHub, read at our last sync. prepare is not recorded; it runs only on a GitHub install, and shows up under build scripts when pnpm blocks it.

README mentions

shell commands (bash, exec, spawn …)

Source: a keyword match on the README — a hint about what the plugin touches, not an analysis of its code.

Not an audit. These are the record of one install and two text scans; nobody has read this plugin's code on your behalf. Plugins run with your agent's permissions.

The AI take

What it is — dsh-mneme is an AI memory engine plugin.

Who it is for — When using DeepSeek Harness, if the agent needs to simulate real brain memory mechanisms, it is suitable to install it. If the user does not use the JavaScript language, they do not need to install it.

Watch out — Sandbox test passed: installed in a new profile and registered into the profile by harness. Static check indicates it will execute shell commands. No obvious pitfalls found.

The verdict — I will not install it because it executes shell commands.

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-mneme does

Conversation fragments are distilled into local layers, consolidated during idle time, then retrieved into one context block.

dsh-mneme is a DeepSeek Harness plugin that provides long-term memory across conversations, projects, preferences and decisions. At the end of a conversation, it distils material worth keeping into a local SQLite database; on later prompts, relevant memories are retrieved and added to the session context. DeepSeek Harness stores ten human-editable Markdown mirrors alongside the database, so the records can be inspected, edited and exported rather than being confined to an opaque vector store.

While idle, autoDream consolidates duplicate memories, compresses stale material and archives older entries. Conflicts are frozen for review instead of being resolved automatically. The plugin also records provenance and replayable consolidation details, and exposes a settings panel for browsing, searching, editing and deleting memories. Local semantic search can use a local embedding model, and dreamProvider, dreamModel, summarizeProvider and summarizeModel control whether consolidation and summarisation use configured providers.

dsh-mneme is intended for developers who want persistent, inspectable context across sessions and can run Node 24+ with DeepSeek Harness 0.1.x or 0.2.x. It is a poor fit where conversation-scoped context is sufficient, or where storing cross-session information locally is undesirable. The terminal surface is the plugin’s CLI, including the standalone dsh-mneme-serve daemon; this can read and write the same memory store under the agent’s permissions. By default the data remains local, with no Mneme API key required.

dsh-mneme documentation

How dsh-mneme behaves

At conversation end, dsh-mneme extracts facts, preferences and decisions that qualify as durable memories. During a later session, retrieval combines relevance with recency, importance and usage so selected memories are injected into the session context. autoDream runs during idle periods to merge duplicates, compress stale records and archive old material. Conflicting memories are frozen for review rather than silently choosing one.

Each record is stored in local SQLite under ~/.dsh/memory, with ten Markdown mirrors in the same directory. Manual edits to the mirrors take precedence when the files are merged back into the database. The settings panel supports recording, browsing, filtering, searching, editing and deleting memories, as well as viewing an entity graph and audit state.

Configuring dsh-mneme

autoDream and autoSummarize are enabled by default. Consolidation and summarisation use the host model by default. Setting dreamProvider and dreamModel selects a direct provider and model for dreaming; summarizeProvider and summarizeModel does the same for summarisation. To keep these operations offline, use a local host model and clear those four provider/model settings, or disable autoDream and autoSummarize.

The local embedding model and runtime cache are stored in ~/.dsh/mneme and are downloaded again if that directory is removed. Connection configuration for the CLI and MCP integration is stored in ~/.dsh-mneme.

Commands and integrations

DeepSeek Harness loads the plugin in the web profile; dsh web starts the web interface. The standalone dsh-mneme-serve daemon keeps the memory store available when DeepSeek Harness is closed. The mneme-memory package provides a zero-dependency stdio MCP server with six memory tools. An HTTP API is also available for other plugins, and the CLI can access the store.

Requirements and data handling

DeepSeek Harness requires version 0.1.x or 0.2.x, and dsh-mneme requires Node 24+ because it uses node:sqlite. The plugin stores SQLite data, Markdown mirrors, embeddings, runtime cache, CLI/MCP connection details and audit information locally. The README states that it has no telemetry, analytics or remote logging. Removing the plugin does not remove ~/.dsh/memory; that directory must be deleted separately to erase the stored memories.

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-mneme

coding-agents

vectorize-io

53k

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 sourcePython24d ago

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
41k

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.

Installed cleanly when we ran it

npm packagePython24d ago

AI review

dsh-memory-plugin

What it is — Connects DeepSeek Harness to an OpenViking server for pre-step recall, profile injection, session capture, viking:// URI guarding, and memory read/write tools.

Who it is for — You keep revisiting the same repo in DeepSeek Harness and lose conventions across sessions, with OpenViking as the place those should live. If in-repo docs and rule files already are your context, or you only open throwaway chats, skip it.

Watch out — It installed on a fresh profile and the harness registered it. A reachable OpenViking server is required, and it executes shell commands.

The verdict — I'll turn it on: the product for me is recall happening before the step, not two more tools the agent might ignore.

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
12k

Local-first memory plugin for DeepSeek Harness: layered L1/L2/L3 memory with automatic capture, manual memos_* retrieval tools, and a built-in memory viewer.

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

GitHub sourceTypeScript21d ago

AI review

memos-local-plugin

What it is — Hooks DeepSeek Harness to on-device MemOS memory so a turn can be captured, recalled around the next task, queried with memos_* tools, and inspected in a viewer.

Who it is for — You keep driving the same repo inside DeepSeek Harness and each new agent turn starts blind because prior decisions are not stored. If memory has to live in a shared team store rather than on your machine, this plugin is the wrong place for it.

Watch out — There is no published package; you wire it up from a subdirectory of the MemOS repo. You must supply an API key or token, and it executes shell commands.

The verdict — The subdirectory tax only pays off if DSH is already where the work happens—I would not install this as a memory experiment.

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
2Source

typescript

agentscope-ai

3.8k

Connects DeepSeek Harness to ReMe's local-first, self-evolving personal knowledge base: automatically captures completed main-agent conversations as user-owned Markdown memory, searches conversations and source material through reme_search with BM25, optional embeddings, and wikilink expansion, and schedules daily memory consolidation.

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

GitHub sourcePythontoday

AI review

typescript

What it is — The plugin integrates DeepSeek Harness with ReMe's knowledge base to automatically capture main-agent conversations as user Markdown memory and schedule consolidation.

Who it is for — When managing main-agent conversations with DeepSeek Harness and wanting to capture completed dialogues as user-owned Markdown memory, this plugin provides integration. For users who do not want to share the workspace with ReMe, independent knowledge base tools offer a different perspective.

Watch out — The plugin requires manually allowing the build script when installing from source. Sandbox testing has not been completed. The plugin executes shell commands.

The verdict — If I am willing to manually allow the build script from source, I would install it because it connects conversations to persistent Markdown memory.

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

ReMe

agentscope-ai

3.8k

Connects DeepSeek Harness to ReMe's local-first, self-evolving personal knowledge base: automatically captures completed main-agent conversations as user-owned Markdown memory, searches conversations and source material through reme_search with BM25, optional embeddings, and wikilink expansion, and schedules daily memory consolidation.

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

GitHub sourcePython12d ago

AI review

ReMe

What it is — Integrates ReMe's local-first self-evolving personal knowledge base with DeepSeek Harness.

Who it is for — When running agents using DeepSeek Harness that require automatic capture of conversations as Markdown memory, this is suitable. If you do not need shared local workspace across agents, you can skip this plugin.

Watch out — No obvious pitfalls found. The plugin will execute shell commands.

The verdict — I would install it, but only if shell command execution is permitted.

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

MemSearch

zilliztech

2.9k

Shared Markdown memory for DSH and other coding agents, with automatic capture, pre-step context injection, searchable recall, and memory-to-skill self-evolution through a review panel.

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

GitHub sourcePython3d ago

AI review

MemSearch

What it is — MemSearch provides shared Markdown memory for DeepSeek Harness coding agents. It supports automatic capture, pre-step context injection, searchable recall, and memory-to-skill self-evolution through a review panel.

Who it is for — When building complex coding agents with DeepSeek Harness that require persistent context across sessions, MemSearch offers value. If your work involves only short-lived conversations without cross-platform memory needs, you can skip it.

Watch out — It will execute shell commands. Sandbox testing has not been done yet; no obvious issues were identified.

The verdict — I would install it because it enables memory to evolve into reusable skills, but only if you are willing to use it via subdirectory installation and accept shell command execution as a trade-off.

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