Introduction

In DeepSeek Harness (DSH), after a regular Session ends, the Agent can easily forget user preferences, project constraints, and validated experiences. dsh-memory addresses this issue by combining Claude Code’s Auto Memory with Codex’s Session memory organization approach, providing DSH with simple, transparent, and context-friendly long-term memory.

Core Capabilities

  • Local Markdown Storage: Authoritative memory is stored in the local $DSH_HOME/memory directory, and users can read and back it up themselves.
  • Global / Workspace Isolation: Global stores cross-project preferences, while project facts remain only in the current Workspace, avoiding information pollution.
  • Progressive Disclosure: The Agent first receives Global memory and the index of the current Workspace; detailed content is read on demand through DSH file tools.
  • Safe Writes: When concurrent modifications are detected, direct overwrites are rejected to prevent data loss.
  • Session Organization: Ended and stable Sessions are selected, and an independent organization Agent extracts memory from them.
  • Observability: Organization results are recorded, with optional Debug logs (conversation content or API keys are not recorded).
  • Bilingual Interface: The Memory page automatically switches according to the DSH Web locale.

Installation and Enablement

  1. Run the installation command:
    dsh plugin --profile web add @hr98w/dsh-memory
  1. After installation is complete, fully restart dsh web to load the plugin.

Usage

  • Save Project Conventions: In a test Workspace, tell the Agent: “Remember, this project’s release check codename is Pinecone, and remind me to check the rollback plan before each release.”
  • Query Conventions: Create a new Session in the same Workspace and ask: “What conventions exist before releasing this project?”
  • Configure the Organization Model: Select the model used for Session organization on the settings page.
  • Manage Cross-Project Preferences: Store general cross-project preferences in Global memory.

Notes

  • Restart Required: After installation or update, dsh web must be fully restarted for the changes to take effect; refreshing the page has no effect.
  • Concurrency Limit: Concurrency protection applies only within the same MemoryStore instance. It is recommended that a single DSH process handle memory writes for the same $DSH_HOME.
  • Data Privacy: Debug is disabled by default and does not record conversation evidence, memory content, or API keys. The Web management interface only allows local access.
  • Local-First: Authoritative memory is stored locally, but this does not mean all model processing is completed offline.
  • Plugin Ecosystem: DSH’s philosophy is “everything is a plugin.” The community catalog is an independent site and has no official affiliation with DeepSeek / High-Flyer.

Summary

dsh-memory solves the Agent long-term memory problem through local storage and a progressive disclosure mechanism. Its open-source MIT license permits free use and modification.

GitHub Repository