DSH Plugins Marketplace

DSH Plugins

Plugins

/

Memory & Context

/

dsh-workbuddy-memory

d

dsh-workbuddy-memory

Manifest valid

Shares one set of Markdown memory files between DSH and WorkBuddy: project memory, user memory and the user profile are injected into the session context, while daily notes stay out of the prompt and

UI (client)hasBundlePatch

dsh-workbuddy-memory

CI

English | 中文

Let DSH share the memory files WorkBuddy already writes — no second copy, no WorkBuddy install needed.

Injection is layered: a small core stays always-on, the rest is listed by topic and read on demand. What you save is context you would pay for every turn, not capability — and it shows most on a long memory file.

What the model sees

A memory file is split in two, and only one half reaches the context every turn:

MEMORY.md
│
├─ ## 常驻记忆 ──────────► injected every turn
│    - the entry needed every time   (a prefix: the scan stops at the first
│    - another one like that          entry that does not fit, and says how
│                                     many were left out)
│
└─ ## some topic ────────┐
   ## another topic ─────┼─► only the section names are injected
   ## a third topic ─────┘   memory_read fetches a whole topic on demand

So the prompt looks roughly like this:

### 项目记忆
## 常驻记忆
- the entry needed every time…

### 可按需查询的主题
- 常驻没写的先看这里:memory_read(target=前缀-memory, section=主题名)…
- project/some topic
- user/another topic

Each line carries a project/ or user/ prefix because memory_read needs a target as well as a section — with a bare name the model has to guess which file to read. A truncated list says it is truncated.

Budget is inject.coreBudget — 4000 units by default, 4000–20000 — split across the project core, the user core, the fixed rules and the topic list. inject.mode: 'full' is the compatibility fallback: every file injected whole, the way earlier versions did.

A file with no core section is injected whole and reported as legacy:* by memory_status; the panel shows it as a banner. Nothing rewrites an old file on its own — the split is your decision.

⚠️ Keep topic bodies to - entries. Add anything else — one prose sentence, a sub-heading, a fenced block — and the whole file falls back to whole-file injection, because a file that cannot be split reliably is not split. This is the behaviour most likely to look like a bug.

Install

dsh plugin --profile web add dsh-workbuddy-memory

Requires DSH >= 0.2.0. Do not hand-write an insert: block into cordis.patch.yml — the config card writes an id-targeted override, and both together become two records with the same id.

Working on the plugin itself:

node scripts/dev-install.mjs web   # links the profile to this checkout

A source edit then needs only a profile restart. Pass --copy for a self-contained install that must be re-run after each edit.

Tools

Five, and only five:

ToolWhat it does
memory_statusresolved paths, active mode, compatibility states, writability
memory_readread one target; returns the revision and the section list
memory_searchliteral search across the memory files
memory_appendappend one entry to a section, or one line to today's note
memory_editreplace or delete one entry

Bulk work — rewriting a section, restoring a backup, archiving old daily notes — happens in the panel, where a person sees the diff before the write. Those are deliberately not tools: the same destructive edit driven by a model has nothing in front of it but its own reasoning.

Panel

A Memory entry in the left rail, a Project memory tab in the right sidebar, and a button in the session header. From there you can edit entries and sections, rewrite the whole file, paste a draft the model produced (diffed, and refused unless the revision it was written against still matches), browse and restore backups, archive old daily notes, and undo a write for ten seconds.

Safety

Every write — tool or panel — goes through the same path: lock → revision check → backup → atomic replace → verify. A destructive rewrite must name the revision it saw; if the file changed underneath, the answer is conflict and nothing lands. There is no "overwrite anyway", by design. Editing memory files with write / edit / apply_patch is refused, so a model cannot route around the tools.

This is a guard against accidents, not a security boundary: it does not stop a shell command.

Files it reads

BlockFile
Project memory<cwd>/<dataFolder>/memory/MEMORY.md
Daily notes<cwd>/<dataFolder>/memory/YYYY-MM-DD.md — not injected
User memory<workbuddyHome>/MEMORY.md
User profile<workbuddyHome>/USER.md or user-<uid>-personal/USER.md — read-only

dataFolder defaults to .workbuddy. An empty workbuddyHome follows WorkBuddy's own order: WORKBUDDY_CONFIG_DIR → CODEBUDDY_CONFIG_DIR → ~/.workbuddy.

Reading creates nothing — no directory, no state, no receipt. The first legitimate write creates the layout, and a refused write creates nothing either.

Configuration

The plugin page's config card covers the common ones:

KeyDefaultMeaning
readOnlyfalsemaster switch; every write refused
inject.modelayeredfull is the compatibility fallback
inject.coreBudget4000layered budget, 4000–20000 UTF-16 units
inject.limits.*10000 / 2000 / 8000 / 2000per-block limits for full mode and legacy files (project / rules / user / profile)
inject.distillAbovetwice limits.useruser-memory size that makes the plugin say the file is due for distillation
inject.profileUid''pick one profile candidate by account uid
workbuddyHome''empty follows the environment
dataFolderName''empty follows WORKBUDDY_DATA_FOLDER_NAME, then .workbuddy
write.backupKeep20backups kept per file; 0 refuses destructive rewrites
ui.allowWriteActionstruemaster switch for panel writes
search.enabledtruewhen off, memory_search is not registered

Everything else (inject.refresh, inject.sanitizePaths, write.*, guard.*, the three ui.* panel entries, search.maxResults) is declared with its default in src/config.js and can be set in the profile's cordis.patch.yml. stateDir and locale are YAML-only and need a reload.

When a write is refused

The panel explains these in your language; the model gets the same codes.

CodeWhat to do
conflictThe file changed. Read it again, then decide — there is no overwrite.
layering_confirmation_requiredThe write would split an unsplit file. Confirm the split once via the panel's draft or source mode.
receipt_capacityThe receipt store is full. Delete finished records from <stateDir>/receipts/ (default ~/.dsh/workbuddy-memory/receipts/) — check unresolved ones first.
backup_requiredwrite.backupKeep is 0. Set it to at least 1; an ordinary append is still allowed.
outcome_unknownRetry with the same operation id; a new one may run twice.

Limits

SituationWhat happens
No panel (headless, or ui.enabled: false)The model can read, search, append and edit single entries; archiving and restoring need the panel
An external editor writes the same fileIt does not take this plugin's lock — only the revision check protects you, and only against changes it can see
Two memory plugins on one file setNot supported. The locks mean nothing to each other, and the same entries get injected twice
The same operationId replayed much laterCommitted receipts are kept 24 hours, up to 2000 — past that it is a new request
The character counts in memory_statusThis plugin's own contribution in UTF-16 units, not a token count or a cost
A read failsDegrades to "inject nothing"; it never breaks a turn

Tested on Windows 11 with Node 24. Not verified on Linux or Node 20.

Development

npm test
npm run test:coverage

Design documents and the implementation log live in docs/.

License

MIT

Comments

Loading…

Similar plugins

@bangbang-03/dsh-memory

DSH 工作区长期记忆:索引式简报省 token、轮末相关召回、memory 工具按需读写、版本链与体检、轮次结束自动提炼(可草稿审批),设置面板里可视化查看与管理。

Terminal & ClientsMemory & ContextManifest valid

★ 0

dsh plugin --profile web add @bangbang-03/dsh-memory

by boogoo619

Workspace-wide sticky notes on an infinite canvas: notes are plain Markdown files, created manually, captured from conversations, or distilled by the AI, and can be handed back as context; ships 12 mo

Development & InfrastructureMemory & ContextManifest valid

★ 3

↓ 270/wk

MIT

JavaScript

Nov 9, 2026

dsh plugin --profile web add dsh-noteboard

by LittleBlackTong

Long-term cross-session markdown memory with an LLM-Wiki structure and a SOUL.md persona, injected at session start (by default only after the first user message and only in the active session), plus

Memory & ContextManifest valid

★ 39

↓ 13.5k/wk

MIT

JavaScript

Nov 17, 2026

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

by XHszDHM

Long-term notes and daily journals kept per workspace in a hot/cold archive, each tier with its own index and rebalanced once a day; read and written through seven memory_* tools, with a settings page

Memory & ContextManifest valid

★ 0

MIT

JavaScript

Nov 4, 2026

dsh plugin --profile web add dsh-memory-tide

by wojiao42

文件型长期记忆:每个会话注入你自己的 Markdown 记忆文件,提供读写工具,并能查出 DSH_HOME 漂移;不读对话、不联网 · File-backed memory for DeepSeek Harness, with verifiable constraints

Memory & ContextSessions & MessagesManifest valid

★ 0

MIT

JavaScript

Oct 7, 2026

dsh plugin --profile web add dsh-memory-file

by dingguangyi0

Migrate WorkBuddy sessions, memories, MCP drafts, and automation tasks into DSH — preview-first, read-only on the source

Manifest valid

★ 0

TypeScript

Sep 12, 2026

dsh plugin --profile web add dsh-plugin-migration-workbuddy