@fonlan/dsh-gitmemo
由 Git 支持的 DeepSeek Harness 长期记忆：本地 .mem git 仓库（单一 main 分支、不可变条目、结构化提交消息），提供 mem_search / mem_read / mem_write / mem_delete / mem_replace 工具，并支持完全自动的旧版迁移（无 CL
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @fonlan/dsh-gitmemo@0.4.0Gitmemo 以 @fonlan/dsh-gitmemo 发布，当前版本为 0.4.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 简体中文
Git-backed long-term memory for DeepSeek Harness (dsh) — a Cordis plugin mirroring
GitMemo. The root agent stores completed task outcomes as
immutable markdown entries in a local .mem Git repository (a single main branch with
structured commit messages) and searches them before starting new work. Git is the only
dependency, and no manual memory commands are ever needed.
search, read, write, delete, replace as part of its normal task flow.mem Git repository; no cloud dependencygit CLImem_search; subagents carry neither the workflow rules nor the tool schemasmem_replace (one commit deletes the old file and adds the new one), withdrawal uses mem_deletemem_replace is not just for user corrections: work that overrules a stored conclusion actively replaces it; mem_search scores hits as distinct matched keywords + a mild recency bonus (≤ +0.5, linearly decaying to 0 over ~180 days), so conflicting stale conclusions lose to their replacementskind: "topic" entry aggregates a topic's "current truth": the summary states the currently-valid conclusions and the page evolves via mem_replace (kind is inherited), not per-task rewrites[[<commit-hash>]]; mem_read with expand: true resolves those links one hop and automatically follows the GitMemo-Replaces chain to a replaced target's active version (dangling links come back with an error)GitMemo-* trailers (keywords, digest, search-text projections); search is git log --grep --fixed-strings over commit messages only — entry bodies are never scanned.mem's Git history; replaced/deleted entries stay readable by hash.mem permanently stays on main; the code branch/SHA is recorded as entry metadata only| Piece | Description |
|---|---|
mem_search | Search memories: keywords (array of 1–12, 中英文同义词), skip + snapshot (stable pagination). Returns up to 20 scored hits with summary / keywords / kind / matched_keywords (score = matched keywords + recency bonus) |
mem_read | Read one memory entry by create/replace commit hash (full markdown; historical hashes stay readable); returns kind; optional expand: true resolves [[hash]] links one hop |
mem_write | Store a task outcome: title + summary + keywords (2–12) + content (engine generates front matter), optional kind ("task" default / "topic" aggregated page), related_branches / related_paths. One ADD commit per immutable file |
mem_delete | Withdraw an obsolete conclusion (requires commit_hash + reason) |
mem_replace | Correct an outdated conclusion in ONE atomic commit (D old + A new) — never delete-then-write. Triggered by user corrections AND by work that overrules a stored conclusion; kind defaults to the replaced entry's kind |
| Scoped rules | The workflow rules + the five tools are registered into root agents only (delegationDepth === 0) at agent/created; subagents carry neither |
Requires dsh ≥ 0.1.0-rc.6 and the git CLI.
From the npm registry (once published):
dsh plugin --profile web add @fonlan/dsh-gitmemo
From a local checkout (development / unpublished):
dsh plugin --profile web add /path/to/dsh-gitmemo
Then restart the dsh profile (e.g. restart the dsh web process). The plugin registers on the
host plane, so every new root agent session in that profile sees the tools and the rules.
The bundle patch ships with sensible defaults; override them in the profile's
cordis.patch.yml:
- id: dsh-gitmemo
config:
searchLimit: 20 # max hits per mem_search call (page size)
lockTimeoutMs: 30000 # cross-process lock wait timeout
projectRoot: null # optional explicit project root (defaults to the session cwd)
The .mem repository lives at the project root of the calling session's workspace
(git rev-parse --show-toplevel, falling back to the working directory; an explicit
projectRoot config wins). The repo layout:
.mem/
├── .git/
├── .gitmemo-format # schema version marker, e.g. "2"
└── entries/ # one immutable file per active memory
└── <utc-ms>-<digest-prefix>-<slug>.md
.mem is initialized on its own main branch; initialization writes .mem/ and the lock
file path into the parent repo's .git/info/exclude (never into a version-controlled
.gitignore), and refuses to run when the parent repo already tracks .mem content.kind ("task" or "topic"); topic
entries additionally carry a GitMemo-Kind: topic commit trailer.The whole memory stays readable with plain git:
git -C .mem log --oneline
git -C .mem show <commit-hash>
mem_search.
Pure chat and general Q&A need no search.title / summary / keywords / score /
matched_keywords, mem_read at most 5 most relevant memories (kind: "topic" entries
are a topic's aggregated entry point — prefer them); paginate with skip +
the returned snapshot.mem_write every completed repo-related task that still lacks a memory and whose outcome is
valuable/reusable (or was explicitly asked to be remembered). Never duplicate an
already-written entry. Never write for pure Q&A, incomplete tasks, non-repo work, or purely
operational git actions. keywords should be task-related words NOT already present in
title / summary (中英文同义词 both fine) — words already there are searchable via
title / summary themselves, so repeating them does not improve recall.mem_replace (never delete-then-write). If it is obsolete with no replacement →
mem_delete with a reason. The same applies — without waiting for the user — when this
session's own work overrules a stored conclusion (implemented/refactored away). When search
returns conflicting old/new conclusions, trust the newer one (score already includes the
recency bonus).kind: "topic" aggregated entry: the summary states the currently
valid conclusions, and the content links the evidence entries as [[<commit-hash>]] with a
one-line status each; evolve topic pages via mem_replace.npm install
npm run build # tsc → lib/
npm test # build + engine/plugin/migration unit tests (node:test)
dsh-gitmemo/
├── package.json # npm package; dsh.bundle.patch wires the profile layer; bin: dsh-gitmemo
├── cordis.patch.yml # composition layer: the dsh-gitmemo row
├── src/
│ ├── index.ts # Cordis plugin: root-agent-scoped mem_* tools + workflow section
│ ├── mem.ts # core engine (protocol, lock/journal, search, write/read/delete/replace)
│ ├── migrate.ts # legacy migration (dry-run/apply, backup refs, CAS swap)
│ └── cli.ts # `dsh-gitmemo migrate` CLI entry
├── lib/ # built output (committed; used by file:/git installs)
└── test/mem.test.mjs # engine + plugin + migration unit tests
MIT