dsh-keepsake

English | 中文

A memory plugin for DSH (DeepSeek Harness). It remembers what you talked about, so your next conversation doesn't start from zero.

The problem

Every new DSH session starts blank. The API convention you settled on last week, this project's directory layout, the preference you'd rather not repeat — all of it has to be re-explained.

This plugin works in the background:

• Capture — when a turn ends, it decides whether anything is worth remembering and writes it to a local Markdown file.
• Carry — on every subsequent turn it injects the relevant memories back into context, so the model "remembers" you.
• Manage — a local panel where you can see, edit, and delete everything that was recorded, and edit your persona.

Memories live as plain Markdown under ~/.dsh/memory/. Open them in any editor, edit them, put them in git. Nothing is uploaded.

Install

dsh plugin --profile web add "https://github.com/axuan-1314/dsh-keepsake/archive/refs/tags/v0.7.1.tar.gz"

--profile can also be headless or desktop. Zero runtime dependencies — no npm install.

To install from main (includes work not yet tagged), swap the tag for heads/main: .../archive/refs/heads/main.tar.gz.

After installing, open a new session and talk for a few turns with real content, then check whether new .md files appeared under ~/.dsh/memory/. The panel lives in DSH settings under the "Memory" section.

Detailed install / upgrade / rollback steps are in docs/install.md (Chinese).

What changed recently

Since v0.7.1:

• Correction loop — previously a wrong memory could only be overwritten by chance on the next extraction, often leaving two contradictory facts. Now you can say "this one is wrong, it's actually X" — via /memory fix in chat, or by clicking "correct this" on a panel search result. Changes are snapshotted and revertible.
• /memory command — keyword search over memories without opening the panel.
• Memory tidy-up — the panel surfaces duplicate entries, stale entries, and index/disk mismatches. One-click index repair touches index lines only, never deletes entries.
• Project knowledge pages — compress a project's memories into 5 stable views (component map, core concepts, conventions, key decisions, in progress). Manually triggered, never automatic.
• Idle review (off by default) — let the model merge duplicates and clean up expired project memories while idle.
• Panel readability — the panel now uses its own opaque background colors. Previously, when a wallpaper plugin made the background translucent white, white text on the resulting light grey measured 3.10:1, and cards had no visible boundary against body text.
• Corrections no longer "half-apply" — every correction write used to degrade into an append, leaving both the old and new facts on disk. Fixed.

Full history in CHANGELOG.md; limits and deliberate non-features in ROADMAP.md.

Features at a glance

Details on triggering, failure behavior, and how to turn each off are in docs/features.md (Chinese).

Configuration

For most people the panel is enough. You'd only edit cordis.patch.yml to pin a model for extraction, adjust injection budgets, or configure a semantic-recall endpoint.

All keys: docs/configuration.md (Chinese).

Where data lives

~/.dsh/memory/
├── global/                    # Global memory (cross-session)
│   ├── persona.md             # Persona
│   └── work-profile/ ...      # Four categories, each an index + entries
├── projects/<project>/memory/ # Project memory (isolated per workspace)
├── runtime/                   # Compiled runtime layer (deletable, rebuildable)
├── pages/                     # Knowledge pages (deletable, rebuildable)
├── backups/                   # Automatic backups
└── trash/                     # Recycle bin

The only source of truth is *.md and MEMORY.md. backups/, trash/, runtime/, and pages/ are copies or derived views — deleting them loses no memory (only the ability to roll back).

Full layout and file format: FORMAT.md.

Privacy: everything stays local. Extraction calls go through your current session's model route — there is no separate upload path. The API and panel bind to loopback only. Failure logs record error summaries, never conversation content.

Docs

The docs/ pages are currently Chinese-only. FORMAT.md and RUNTIME-FORMAT.md are the interface specs and are precise enough to read alongside the code.

Development

npm test        # node --test, full unit suite
npm run check   # syntax check for lib/*.js

Zero dependencies — clone and run, nothing to install.

Related

Another DSH plugin by the same author, fully independent: dsh-usage-stats — token heatmap, trends, and per-model breakdown.

License

MIT