DSH Marketplace

dsh-memory-evolve

csyangwen/dsh-memory-evolve

A purely plugin-based implementation that brings "cross-session long-term memory + background self-evolution" capabilities to DeepSeek Harness: five-track memory · git branch awareness · in-turn self-review · skill self-evolution and skill manager · four-track to-do · COI scheduling · session broadcast · session search · prompt manager · temporary info notes—zero core modifications, zero runtime dependencies, ready to use upon installation and completely removable upon uninstallation.

44548JavaScriptMITSource

Install

Add dsh-memory-evolve 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 8d 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-evolve

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

Security

What installing dsh-memory-evolve runs

Build scripts

No build script was blocked in our run.

Source: our sandbox install on DeepSeek Harness 0.2.2-rc.1, 8d 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 — The plugin provides cross-session long-term memory and background self-evolution support for DeepSeek Harness.

Who it is for — Developers switching sessions to maintain multiple projects suit this plugin, as the AI remembers project key facts and todos. If you seek tools without shell execution, this plugin requires executing shell commands.

Watch out — When installing from source, you need to manually allow the build script first. The sandbox test passed: installed in a new profile and registered into the profile by harness. No obvious pitfalls found.

The verdict — I would install it if cross-session memory is needed, since it is completely removable with zero core modifications.

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

Abstract diagram of memory, tasks and agent sessions flowing through branching workspaces into an archive.

dsh-memory-evolve is a DeepSeek Harness plugin that adds cross-session memory, task tracking, session coordination and background self-review without modifying the core or adding runtime dependencies. DeepSeek Harness loads it through the package’s cordis.patch.yml, which declares a dsh.bundle.patch; installation registers the plugin on the host automatically.

The plugin reads project context such as the working directory and Git branch, then writes persistent user, global, project and daily memory, project logs, four-track to-dos, skills, prompts and temporary notes. It can inject selected information into later turns, search local files, create and coordinate sessions, broadcast messages, dispatch work to external agents, and synchronise selected memory tracks through Git repositories. In-turn review is configured with reviewEnabled and reviewInterval; review is disabled by default. Many capabilities are also disabled until enabled in the plugin settings.

dsh-memory-evolve is intended for developers who work across projects or sessions and want persistent context, structured follow-up work or multiple AI sessions. It is a poor fit when persistent project data, session orchestration or external-agent dispatch is not wanted. The wake-up chain for idle sessions requires the main DeepSeek Harness process to remain running. The listed terminal-surface risk reflects access to terminal-facing agent workflows and local project files; installation should therefore be limited to profiles whose permissions match that use.

dsh-memory-evolve documentation

Configuring dsh-memory-evolve

DeepSeek Harness registers dsh-memory-evolve from the bundled cordis.patch.yml after dsh plugin add; no manual insert entry is needed. Profile configuration belongs in cordis.patch.yml and overrides the bundle entry by id:

Key Default Effect
reviewEnabled false Enables in-turn memory review
reviewInterval 10 Reviews memory after this many user turns when review is enabled

Set disabled: true on the dsh-memory-evolve entry to stop loading the plugin temporarily. The README also describes settings for enabling individual capabilities, including memory synchronisation, but does not provide a complete key list for those settings.

Commands for dsh-memory-evolve

DeepSeek Harness manages the package with dsh plugin. The documented removal command is dsh plugin --profile web remove dsh-memory-evolve; removing the plugin cleans up its effects. After adding or changing the plugin, restart dsh web for the change to take effect. Existing profiles that manually inserted the plugin must remove that old insert entry, or the duplicate loader ID can prevent startup.

How dsh-memory-evolve behaves

At the end of turns, the plugin records progress in project and daily logs. Project data is separated by working directory, and logs can include the current Git branch. Important project memories require confirmation before they become active context. Archived memories stop being injected until restored. Optional synchronisation stores selected memory tracks in dedicated Git branches, with an optional shared memory repository separate from project code.

The plugin can create internal sessions, place them in collaboration rooms, send broadcasts and coordinate external agents. Results can be written to project and daily logs. The README does not specify a minimum DeepSeek Harness version, operating-system support, environment variables or a complete on-disk file layout.

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

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 sourcePython22d 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 packagePython22d 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 sourceTypeScript19d 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

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

typescript

agentscope-ai

3.6k

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

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

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 sourcePythonyesterday

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