Elysia's memory plugin for dsh. One shared, human-editable MEMORY.md across every session: two-disk mirror, history snapshots, cross-process write lock; entries tier between the main file and a searchable archive by hit frequency; retrieval is keyword co-occurrence plus BM25. Nine sections (persona, requirements, corrections, lessons, methods, requests, sessions, method library, ingested docs) plus a dedicated self-identity section for a character's own self-cognition, injected above the persona. Ships an opt-in memory pack (packs/elysia: 61,903-char identity + 2,482-char persona, distilled from 1,696 officially-confirmed voice lines and 112,175 dialogue lines — not written by hand, measured) that is off by default, backs up before writing, only touches identity/persona, and can be uninstalled. Also opt-in voice playback through a local GPT-SoVITS engine, a skills library, and a sticker library that sends a fitting sticker at the right moment.
Install
# from a prebuilt release tarball
dsh plugin --profile web add "https://github.com/1148462398-hub/dsh-elysia/releases/download/v2.1.3/dsh-elysia-2.1.3.tgz"
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:1148462398-hub/dsh-elysia
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★ 58867
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★ 41559
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.
MemTensor/MemOS#memos-local-plugin★ 12258
Local-first memory plugin for DeepSeek Harness: layered L1/L2/L3 memory with automatic capture, manual memos_* retrieval tools, and a built-in memory viewer.
agentscope-ai/ReMe#dsh★ 3750
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★ 2820
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★ 1404
Reads the session files forty-two 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).
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.