dsh-obsidian-mem: Transforming Project Memory into an Obsidian Vault

Introduction¶

The plugin ecosystem of DeepSeek Harness (DSH) allows developers to modularize specific features. For scenarios that require managing project documentation and long-term memory, common approaches often rely on temporary context or custom databases. A plugin that stores project documentation and long-term memory as plain Markdown in a dedicated Obsidian vault would allow viewing and managing this data directly without running DSH, while also leveraging Obsidian’s search and view capabilities.

Plugin Overview¶

dsh-obsidian-mem is a host plugin for DeepSeek Harness maintained by bonerrush. It belongs to the memory category.

Its core value lies in: keeping project documentation and long-term memory as plain Markdown stored in a dedicated Obsidian vault.

Core Features¶

1. Persistent storage: Keeps project documentation and long-term memory as plain Markdown in a dedicated Obsidian vault.
2. Project binding: Creates a stable projectId for a repository.
3. Directory structure: Writes project documentation to a dedicated vault directory.
4. Toolkit: Provides six mem_* tools.
5. Search index: Builds a search index using node:sqlite.
6. Automatic distillation: Automatically summarizes completed conversation turns.

Installation and Configuration¶

Before installing, ensure the environment meets the following requirements:
* DeepSeek Harness: >=0.1.5-rc.2 or >=0.1.7-rc.2
* Node.js: >=22.22.2

The plugin code is loaded only once per process, so DSH must be restarted after installation.

1. Install the plugin¶

Use the official command to install it:

dsh plugin --profile memcheck add github:bonerush/dsh-obsidian-mem

2. Verify installation¶

After installation, check whether the configuration includes the plugin:

dsh --profile memcheck --dump-config | grep -n obsidian-mem

If the output contains the configuration line for obsidian-mem, the installation was successful.

3. Configure the Vault¶

Choose a local disk directory as the dedicated vault directory (default: ~/Documents/dsh-memory) and open that directory in Obsidian.

4. Restart the process¶

DSH must be restarted (for example, dsh web) for the plugin code to be reloaded and take effect.

Usage and Examples¶

After installation and restart, you can use it in the following ways:

1. View the project list:

mem_admin(action="projects")

2. Start a session: Start a session in any Git repository, then ask questions directly or use tools.

Notes¶

• Honest limits: Before enabling automatic writing, read the Honest limits section in the plugin documentation to understand its refusal policy.
• Data is not exhaustive: The plugin is relatively new, and the content currently written is not exhaustive. All changes are recorded in CHANGELOG.md.
• Local storage: The vault must be local.
• Dedicated directory: Do not point the vault to an existing personal vault you already maintain. The plugin will create project directories.
• Permissions and source code: The plugin code runs with the permissions of the DSH process. Before installing, review the source code and license.

Conclusion¶

By transforming DSH’s memory capabilities into a standard Obsidian vault, dsh-obsidian-mem solves the persistence problem for project documentation and long-term memory. It uses plain Markdown and SQLite to provide a structured storage solution, suitable for scenarios that require seamless collaboration between DSH and Obsidian.

• Plugin directory page
• GitHub repository