Preamble

In the DeepSeek Harness (DSH) plugin ecosystem, memory capabilities typically need to address two problems: how to retain useful conclusions after a session ends; and how to retrieve only relevant content when subsequent Agents need historical context. dsh-memory-eternal is a memory plugin designed for this scenario. It deposits conversations into a local Markdown Vault, uses custom deduplication and custom CJK retrieval, and allows Agents to recall historical context on demand via the memory_recall tool.

What is this

dsh-memory-eternal is maintained by EternalNight996 and is licensed under MIT.

Its positioning is as a DSH memory plugin, without porting any existing memory frameworks. Memory content is stored in local Markdown files, which can be managed via git. The plugin does not modify DSH source code, allowing one memory library to be shared by multiple Agents.

Core Features

Auto-deposit and Recall on Demand

  • Automatically deposits knowledge cards to the local Markdown Vault after a conversation ends.
  • Agents recall historical context on demand via the memory_recall tool.
  • After installation and restart, daily depositing does not require manual triggering.

Graphical Knowledge Base

  • The settings page provides a graphical knowledge base, including statistics, search, and knowledge graph.
  • The sidebar supports one-click popup.
  • The “Memory” button at the bottom of the sidebar enters the memory library.
  • DSH Settings → Memory is a pure configuration page.

Review and Recycle

  • New cards default to the review center (pending), moving to the main library after manual approval.
  • Support for rejected and trash items.
  • Trash items are soft-deleted; they can be recovered within 30 days, and are automatically permanently deleted after the expiration period.

Multi-Agent and Browser Interface

  • Supports DeepSeek Harness (DSH), Claude Code, Codex CLI / Cursor.
  • Provides a standalone browser interface, with data syncing with DSH embedded pages.
  • Supports self-management features: autoWebMode, watchdogAutoSpawn, autoMcpSetup.
  • Provides one-click recommended configurations: A (Lightweight and peace of mind) / B (Extreme savings) / C (High quality).

Installation and Enablement

Installing in DSH

Install to the web profile in DSH CLI:

dsh plugin --profile web add dsh-memory-eternal

When updating in a DSH profile, the requirement is to use pnpm; npm install will result in EUNSUPPORTEDPROTOCOL. You can also update by entering the profile directory:

cd ~/.dsh/profiles/web && pnpm add dsh-memory-eternal@latest

After restarting dsh web, auto-deposit of knowledge cards, the memory_recall tool, and the graphical interface take effect immediately.

Using in Other Agents

Install the CLI separately:

npm i -g dsh-memory-eternal

Then connect to the corresponding tools:

dsh-memory connect claude
dsh-memory connect codex
dsh-memory connect cursor

These commands are used to mount dsh-memory into Claude Code, Codex CLI / Cursor. Auto-mounting MCP is off by default; enabling it will affect Claude Code / Codex / Cursor configurations.

Typical Usage

Retrieval and Manual Capture

dsh-memory recall "database selection"
dsh-memory capture "important conclusion..."

recall is used for retrieving memory; capture is used for manually depositing content.

Auto-mounting and MCP Connection

dsh-memory setup [--dry-run]
dsh-memory connect claude
dsh-memory connect codex
dsh-memory connect cursor
dsh-memory mcp

setup is for rerunning or previewing auto-mounting; connect is for connecting to Claude Code, Codex CLI / Cursor; mcp is for MCP connection.

Web Interface and Service Keep-Alive

dsh-memory serve [--port 7999]
dsh-memory open
dsh-memory watchdog [--port 7799]

serve is for running the Web in the foreground; open is for opening the browser standalone interface; watchdog is for keep-alive. The watchdog is a separate node process, consuming about +47 MB of memory.

Changes to autoWebMode and watchdogAutoSpawn require a DSH restart to take effect.

Suitable Scenarios and Notes

Suitable for DSH users who need local memory, a shared memory library across Agents, and want memory files to be readable and git-manageable.

Notes before use:

  • Requires Node >= 22.
  • Depends on @deepseek-ai/schemastery, with peerDependencies including @deepseek-ai/cordis, @deepseek-ai/dsh-llm, @deepseek-ai/dsh-tools.
  • Distilling knowledge cards or feeding semantic deduplication to AI will call AI, potentially incurring costs; turning it off can reduce calls.
  • zcode (Zhipu) currently has no native MCP; it can be converted to MCP via the community zcode-open-bridge or use the CLI.
  • The plugin runs with the permissions of the current dsh process; you should check the source code and license before installing.

Get it

  • GitHub: https://github.com/EternalNight996/dsh-memory-eternal
  • Directory page hint: https://www.skillhub.cn/plugins/EternalNight996/dsh-memory-eternal (The URL is from the plugin hint and has not been verified in this document)