DSH Marketplace

dsh-memory-meow

Phant0Meow/dsh-memory-meow

Project-scoped cross-session memory: six-layer SQLite store (soul/user/project/fact/lesson/topic) on node:sqlite, cache-friendly first-message injection, memory_remember/search/find_similar/read/update tools, and per-window nightly consolidation ("dream").

21118TypeScriptMITSource

Install

Add dsh-memory-meow to DeepSeek Harness

Install into

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 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-memory-meow

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

Security

What installing dsh-memory-meow 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

Neither shell commands nor credentials.

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 — Provide cross-session SQLite memory storage and tool support for DeepSeek Harness.

Who it is for — If you are doing multi-turn project discussions in DeepSeek Harness requiring maintenance of user and project level memory, you can use this plugin. Users who only perform single-turn tasks may find it unnecessary.

Watch out — Tested successfully in a fresh profile where it registers with Harness. If using pnpm, manual build allowance is needed. No obvious pitfalls found.

The verdict — I would install it because it offers a self-contained solution with per-window consolidation for long sessions.

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-memory-meow does

Layered memory tiles flow through a sieve into a project archive.

dsh-memory-meow is a DeepSeek Harness plugin that stores and recalls project-scoped memories across sessions. It maintains seven SQLite layers—soul, user, project, fact, lesson, topic, and rules—using node:sqlite. Data is stored under the configured projectDir (default .dsh-meow, relative to the workspace), with optional global data-directory selection through memory_home.

DeepSeek Harness receives a static meow-memory:guide section in the system prompt, while the first user message gets a separate memory snapshot containing long-term soul, user, and rules material. From the second user message, keyword matching retrieves up to hitTopK relevant entries from the global store and the anchored project. The memory_remember, memory_search, memory_project, memory_find_similar, memory_read, memory_update, and memory_dream tools expose storage and retrieval. After at least three hours of window idleness, dream can consolidate memories outside configured peak hours; /dream triggers it manually.

The plugin suits agents that need persistent project context, corrections, preferences, and ongoing topics across sessions. It is a poor fit when memory must not be persisted or automatically injected, or when the additional dream and keyword-matching behaviour is undesirable. The README documents compatibility with DeepSeek Harness 0.1.5, including 0.1.5-rc.1, and describes a self-contained build with no native modules.

dsh-memory-meow documentation

Configuring dsh-memory-meow

DeepSeek Harness exposes the plugin settings through its settings page and profile patch or cordis.patch.yml. The documented options include:

Key Default or documented behaviour
enabled true
projectDir .dsh-meow, relative to the workspace
promptLang zh; also supports en and pt-br
hitTopK 2
dream.enabled true
dream.idleMinutes 180

Additional documented fields include titleMax, autoMigrate, homeDir, disabledWorkspaces, backup, and delegate. promptLang selects the language of injected text, reflection and tool descriptions, and affects the language used for memory entries and keyword extraction. Invalid directory names silently fall back to the Chinese prompt set.

Commands and tools

DeepSeek Harness provides these plugin tools:

  • memory_remember writes a memory with content, project, keywords, and importance; duplicate entries are merged.
  • memory_search performs keyword retrieval with level, project, status, and days filters.
  • memory_project returns a complete project injection section and requires project.
  • memory_find_similar, memory_read, and memory_update support duplicate detection, metadata reads, and status or keyword corrections.
  • memory_dream starts consolidation for the current window.
  • memory_home views or switches the global data directory.

Typing /dream in the input starts consolidation immediately, without peak-hour suppression.

How dsh-memory-meow behaves

The plugin injects memory as an independent plugin snapshot before the actual user message and does not rewrite the user prompt. After compression, the next turn re-injects the long-term snapshot, the project overview consulted in the session, and memories written during that session. Session-level seen-entry tracking is stored in sessions/<id>.json.

Requirements and limits

DeepSeek Harness compatibility is documented for 0.1.5, including 0.1.5-rc.1, with older-version compatibility also described. The runtime build uses node:sqlite and a self-contained lib/index.js produced by esbuild, with no native modules. Automatic dream requires a window idle period of at least 180 minutes and is suppressed during the default peak periods of 09:00–12:00 and 14:00–18:00 Beijing time.

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-memory-meow

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