Project-level memory built around a ledger whose structure the AI designs per project; the plugin only handles detection, injection, write-back, archiving and git. Memories are split by meaning: the active ledger holds current state, the turn journal is append-only, and decisions, the goal tree and lessons are one-card-per-file (with a multi-dimension index over the card folders); the fundamental principles file can be changed only by the user. There is a single compaction mode: before compacting, the AI sorts the work into three buckets - what must stay in context and is re-injected verbatim, what is written to the project's _stash/ for later lookup, and what is dropped. When a conversation is opened in a container workspace holding several projects, it can be locked to one sub-project (the lock lives in the plugin's own home and survives restarts; it leaves no marker in your project). Also an activity log with five levels, where L4 stores the user's own words verbatim (never injected, queryable on demand). Before each compaction a verbatim capsule (user quotes, raw errors, changed files) is written to disk, and both the capsule and its source material survive a restart; a handoff document lets a new conversation resume the previous one. 21 tools, 12 subcommands, 39 settings (one of them switches whether the settings panel or each project's manifest wins). Runs locally, no runtime dependencies.
Install
# from a prebuilt release tarball
dsh plugin --profile web add "https://github.com/18477514055/dsh-ledger-memory/releases/download/v1.2.3/dsh-ledger-memory-1.2.3.tgz"
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:18477514055/dsh-ledger-memory
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
Links
More in this category
vectorize-io/hindsight#coding-agents★ 50543
Hindsight, agent memory that learns: long-term project memory with auto recall and retain, knowledge pages, deep reflection, and per-repo memory banks.
volcengine/OpenViking#examples/dsh-memory-plugin★ 40125
OpenViking memory and context bundle for DeepSeek Harness: pre-step auto-recall and profile injection, session capture, `viking://` URI guarding, and recall/write memory tools backed by an OpenViking server.
agentscope-ai/ReMe#dsh★ 3632
Connects DeepSeek Harness to ReMe's local-first, self-evolving personal knowledge base: automatically captures completed main-agent conversations as user-owned Markdown memory, searches conversations and source material through reme_search with BM25, optional embeddings, and wikilink expansion, and schedules daily memory consolidation.
zilliztech/memsearch#MemSearch★ 2756
Shared Markdown memory for DSH and other coding agents, with automatic capture, pre-step context injection, searchable recall, and memory-to-skill self-evolution through a review panel.
vshulcz/deja-vu#extensions/dsh★ 1220
Reads the session files thirty-three other coding agents on this machine already wrote — Claude Code, Codex, Cursor, VS Code Copilot Chat, opencode, OpenClaw, Hermes, Kimi, Cline, Zed and more — including sessions from before it was installed: six tools (deja_recall, deja_session, deja_blame, deja_fix, deja_how, deja_remember), a /deja command, and optional automatic recall added to the runtime context. Local BM25 index, no LLM, no embeddings, no network (dsh plugin --profile web add dsh-deja).
adoresever/graph-memory★ 652
Traceable, searchable cross-session memory for DeepSeek Harness — conversation knowledge as typed graph nodes (TASK/SKILL/EVENT) and typed edges.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.