dsh-workspace-memories
DeepSeek Harness 的每个工作区持久记忆：通过侧边栏面板管理 Markdown 记忆文件，自动注入工作区的每个会话，并提供用于保存新记忆的代理工具
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-workspace-memories@1.1.1Workspace Memories 以 dsh-workspace-memories 发布，当前版本为 1.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
Per-workspace persistent memory for DeepSeek Harness (DSH) — a plugin that gives every workspace its own durable memory files, injects them into every session running in that workspace, and lets both you and the agent manage them.
DSH agents are stateless across sessions: everything a session "learns" — your project's decisions, conventions, hard-won debugging facts — lives only in that conversation's context and is gone when it ends. The built-in mechanism for durable knowledge is AGENTS.md, but it is a static, project-owned instruction file: the agent cannot update it on its own, and some things should not live in the project folder at all — server addresses and topologies, local environment quirks, machine-specific paths, personal working conventions. Anything under the project tree risks being committed to git by accident.
This plugin closes that gap with a small, explicit memory loop whose default storage is outside the project directory:
~/.dsh/workspace-memory/<workspace>/), never inside the repo. Plain Markdown you can read, diff, and back up. (An opt-in workspace storage mode keeps memories in <workspace>/.dsh/memory/ for teams who want them versioned alongside the code.)AGENTS.md, so a fresh session starts already "remembering".save_workspace_memory tool lets any session persist a decision, server detail, convention, or preference the moment you say "remember this".| Capability | Where |
|---|---|
| Browse / create / edit / delete memory files | Workspace Memory sidebar panel (switch workspaces via the selector) |
| Ask the agent to remember something | Any session: "remember: …" → the agent calls save_workspace_memory |
| Automatic recall | Every session in the workspace gets its memory files injected into its system prompt |
Works in every built-in agent preset (Standard, PTC, Minimal, Creator): the tool is registered in the root composition, and global tools are visible to all presets unless a custom preset opts out with a tools.restrict allow list — add save_workspace_memory to that list if so.
The package is plain JavaScript with no build step, so every install channel works:
# from npm (once published)
dsh plugin --profile desktop add dsh-workspace-memories
# straight from GitHub (no build script needed — sources ship as-is)
dsh plugin --profile desktop add github:lengfengng1-ai-architect/dsh-workspace-memories
# from a local checkout
dsh plugin --profile desktop add ./dsh-workspace-memories
Or use the GUI: sidebar Plugins → Add plugin, paste a package name, GitHub address, or absolute local path, then Enable now.
Uninstall: the Plugins page, or dsh plugin --profile desktop remove dsh-workspace-memories.
.md memory (the extension is added when missing); select a file to edit, save, or delete it.storage: home (default, DSH data directory, outside the project) or storage: workspace (inside the project at directory, default .dsh/memory).Tool registration takes effect immediately on the host, but a model's visible tool list is assembled when each conversation turn starts:
ToolArgsMap) that does not yet contain save_workspace_memory — the model may conclude "there is no memory tool", or fall back to probing the tool by name through the code channel (which actually works, since dispatch goes through the live host registry).save_workspace_memory appears normally — no probing needed.Memory injection into the system prompt is attached when an agent is created (session start, resume after a restart, clear, or compaction); once attached, a session picks up changed memory files on its next step automatically.
Two storage modes, chosen by the plugin's storage config:
| Mode | Memory location | Use it for |
|---|---|---|
home (default) | ~/.dsh/workspace-memory/<workspace-key>/ — outside the project | Machine-local or sensitive notes: server configs, environment quirks, personal conventions |
workspace | <workspace>/.dsh/memory/ — inside the project | Team-shared memories meant to be committed alongside the code |
~/.dsh/workspace-memory/ # default memory store, one subdirectory per workspace
dsh-workspace-memories/ # this plugin
├── package.json # bundle manifest (dsh.bundle.patch + dsh.client)
├── cordis.patch.yml # plugin row declaration
├── index.js # host: /api routes + prompt injection + the save tool
├── client.js # browser: sidebar entry + management panel
├── locale/ # panel copy (en, zh)
├── icon.svg
└── selftest.mjs # host-logic self-test: node selftest.mjs
Safety constraints: the browser panel can only address registered workspaces by workspaceId (no arbitrary host paths); file names are strictly validated (no path separators, .., whitespace, or control characters); one file is capped at 1 MiB; prompt injection truncates each file to 32K characters and caps at 20 files.
link: dependency (local-path install does this): editing client.js hot-reloads in the page via the client HMR receiver; editing index.js (host code) requires a DSH restart to load the new module generation.node selftest.mjs (mocks the plugin context; covers routes, prompt rendering, tool writes, and validation failures).include:workspace-memory should be active; the client slot sidebar.panellist should list a workspace-memory occupant; save_workspace_memory should appear in the tool list.MIT — © 2026 lengfengng1-ai-architect
This is a community plugin built on DeepSeek Harness; it is not an official DeepSeek product. Naming follows the DSH brand guidelines.