Preface

DSH’s Session can already save the raw history of the current session, but for user habits, task experience, and engineering insights that need to be reused across sessions, a checkable and traceable local storage method is still required. DSH ExpMem is a community plugin for DeepSeek Harness that writes long-term personal memory to local JSON files, while retaining DSH Session as a verbatim Recall layer without duplicating Session events. Below is an introduction to its positioning, core capabilities, installation methods, and typical import usage.

What is it

  • Plugin Name: creativedswork/dsh-expmem
  • Maintainer: creativedswork
  • Description: Experience Memory for DeepSeek Harness
  • License: MIT
  • Note: This is not an official DeepSeek project; it is a community plugin within the DSH plugin ecosystem and is not equivalent to the official app store.

Core Capabilities

DSH ExpMem primarily solves the problem of “how long-term memory is written to local files and can be checked, referenced, and recovered.” Verified capabilities include:

  1. Provides long-term personal memory for DSH, saving user habits, reusable task experience, and engineering insights into checkable local files.
  2. Retains DSH Session as a verbatim Recall layer without duplicating Session events.
  3. Provides hierarchical memory:
    - DSH Session JSONL saves raw history;
    - ExpMem saves habits, experience, and insights as JSON files per record.
  4. At a 70% context pressure prompt, encourages the current Agent to retain persistent knowledge and use Recall to recover it.
  5. When retrieving long-term memory, it sorts based on relevance, recency, and importance assigned by the Agent.
  6. Supports auditable reflection:
    - Insight records reference observations or previous reflections;
    - Reflection Runs can be interrupted and resumed.
  7. Maintains the trust lifecycle, with record statuses including:
    - candidate
    - verified
    - disputed
    - superseded
    and retains source, conflict, and replacement history.
  8. Supports importing Markdown memory files from Claude Code and Codex, generating candidate experience records with source evidence.
  9. Runs locally and lightweight, without adding a vector database, background worker, or a second model request, nor modifying the DSH Agent Loop.

Installation and Enablement

First, install the plugin to DSH’s web profile:

dsh plugin --profile web add @creative-dswork/dsh-expmem

After installation, start DSH normally:

dsh web

This installation step accomplishes two things:

  1. Adds DSH ExpMem to the current DSH plugin collection;
  2. Allows DSH to use Recall, retrieval, context pressure prompts, and reflection mechanisms related to long-term memory while running.

Typical Usage

Importing Claude Code and Codex Markdown Memory

ExpMem supports importing Markdown memory files generated by Claude Code and Codex into candidate experience records. It is recommended to perform a dry-run first to confirm the content to be imported:

pnpm dlx @creative-dswork/dsh-expmem import all --dry-run

After confirming there are no errors, proceed with the actual import:

pnpm dlx @creative-dswork/dsh-expmem import all

The default import paths are:

Claude Code:
~/.claude/projects/**/memory/*.md

Codex:
$CODEX_HOME/memories/**/*.md
or
~/.codex/memories/**/*.md

If using custom directories, you can specify them separately:

pnpm dlx @creative-dswork/dsh-expmem import claude --claude-dir /path/to/memory

pnpm dlx @creative-dswork/dsh-expmem import codex --codex-dir /path/to/memories

If you need to attach an explicit project scope to imported memories, you can use:

pnpm dlx @creative-dswork/dsh-expmem import all --workspace /path/to/project

After import, each source file will generate a corresponding candidate experience record, retaining source evidence information. ExpMem will not modify or delete the imported source files.

Suitable Scenarios and Notes

Suitable scenarios for using DSH ExpMem include:

  1. Want to retain user habits, task experience, and engineering insights as local checkable files.
  2. Want DSH Session to remain as the original verbatim history, without being copied or rewritten by the plugin.
  3. Want to migrate usable experience from Claude Code or Codex Markdown memories.
  4. Do not want to introduce a vector database, background worker, or additional model requests.

Notes before use:

  1. DSH ExpMem is not an official DeepSeek project.
  2. License is MIT.
  3. The plugin runs with the permissions of the current DSH process; you should check the source code and license before installation.
  4. ExpMem does not modify or delete the imported source files.
  5. Compatible default values are used when reading 0.2.x and earlier v1 records; scan warnings will be generated for anomalies or future version files, but valid records in the same directory will not be hidden.

Conclusion

The value of DSH ExpMem lies in separating long-term memory from “session history,” saving it as local, checkable, referenceable, and recoverable records, without changing the original historical positioning of DSH Session. It is suitable for developers who wish to extend DSH’s long-term memory capabilities in a lightweight manner.

GitHub Repository:

https://github.com/creativedswork/dsh-expmem

Directory Page:

https://www.skillhub.cn/plugins/creativedswork/dsh-expmem