DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
M

dsh-memory-forge

Memory Forge

将记忆转化为 DeepSeek Harness 的技能:记录对话轮次,回忆重要内容,将流程整理为实际的 SKILL.md 文件

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:Ricky74192/dsh-memory-forge#677f171f7150b115022df5a707a6522fe57ee421
README兼容性版本

兼容性与来源证明

Memory Forge 以 dsh-memory-forge 发布,当前版本为 0.1.1。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/10/29

版本

0.1.1stable
2026/10/29

相关插件

正在加载相关插件…

最新版
0.1.1
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/10/29
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 memory-context 分类下经过校验的插件。

Hindsight Coding Agents@vectorize-io/hindsight-coding-agents面向编程代理的仅反思式 Hindsight 长期记忆(可插拔支持多种运行框架:opencode、……),自动在后台导入(无需设置 CLI)。Contextdsh-context用于上下文洞察和管理的 DeepSeek Harness 插件,提供上下文仪表板和上下文命令,帮助了解上下文的构成及其演变过程。Memory Plugin@openviking/dsh-memory-plugin适用于 DeepSeek Harness 的 OpenViking 记忆与上下文套件Mnemondsh-mnemon面向 DeepSeek Harness 的可组合、基于视图的上下文。开箱即用的可插拔来源与策略、分层记忆和自我演进技能。

README

dsh-memory-forge

Memory that becomes skill for DeepSeek Harness (dsh).

dsh-memory-forge is a dependency-free Cordis Host plugin built around one loop: what happens in a session is captured, what is relevant to the next request is recalled, and what proved repeatable is forged into a real SKILL.md that the harness loads in later sessions.

  • Automatic capture - user prompts and assistant replies are written to a local, inspectable memory store, once per event.
  • Relevant recall - before a step, memories matching the current request are injected as a framed <system-reminder> block, not a recency dump.
  • Memory tools - memory_save, memory_search, memory_forget for explicit, model-driven use.
  • Skill forging - memory_distill_skill turns a proven procedure into a SKILL.md bundle in the user skill root.

Everything stays on the machine: JSONL under $DSH_HOME/memory, skills under $DSH_HOME/skills (or $DSH_AGENTS_HOME/skills). No network calls, no embedding service, no native modules.

Why this exists

DSH deliberately ships no memory plugin. It ships the primitives - AGENTS.md instruction loading, a skill registry that watches the filesystem, a plugin system with hot reload - but nothing that closes the loop from "what happened in this session" to "what the next session knows, and can do".

Hermes-style memory plugins (for example the MemOS local plugin) close that loop with an LLM + embedding + SQLite stack. dsh-memory-forge closes it with a much smaller footprint, and it closes it one step further:

Hermes / MemOS local plugindsh-memory-forge
Full conversation capture, chunked and embeddedTurn capture into append-only JSONL; no embeddings
Auto-recall injected into the system contextAuto-recall injected as a durable user message before step 1
Hybrid retrieval (FTS5 + vector, RRF, MMR, decay)BM25-style lexical retrieval + query coverage + recency half-life
memory_search / task_summary / skill_getmemory_search / memory_forget / memory_distill_skill
Task summarization pipelineNot included; compaction already owns context compression
Skill auto-evolution (generate + upgrade)Model-driven forging into real SKILL.md bundles, discovered by the harness
SQLite + bridge daemon + viewerPlain files; read them with any editor

The trade-off is explicit: no semantic search and no background summarization, in exchange for zero dependencies, zero daemons, a format you can git diff, and a plugin that installs into any DSH profile.

An unrelated package named dsh-memory exists on npm (SQLite FTS5 store, pinned-plus-recent recall). This project is independent and differs where it matters for retrieval: recall is query-relevant rather than recency-ordered, and procedures can be distilled into real skills.

Install

Requires DSH with @deepseek-ai/dsh-base (any shipped profile: web, headless, tui, ...) and Node.js >= 22.

Plugin manager (recommended)

In the DSH Web UI, open Plugins -> Install bundle and point it at this directory, or ask a Creator-preset session to run:

plugin_manager action=install_bundle target=<absolute path to this checkout>

From GitHub or npm

# once the npm release lands, the shortest path:
dsh plugin --profile <profile> add dsh-memory-forge

# straight from the repository:
dsh plugin --profile <profile> add git+https://github.com/Ricky74192/dsh-memory-forge.git

# without git installed, pin the release asset:
dsh plugin --profile <profile> add https://github.com/Ricky74192/dsh-memory-forge/releases/download/v0.1.1/dsh-memory-forge-0.1.1.tgz

The repository and archive installs were verified against this project; a bare dsh plugin add dsh-memory-forge requires the npm release.

The desktop profile is owned by the Electron application; use the Plugins page or plugin_manager for it instead of the CLI. dsh plugin forwards to pnpm, so pnpm must be on PATH. A file: dependency is installed as a copy, so reinstall after editing the checkout.

Manual (development)

node scripts/dev-install.mjs --profile memdev --debug \
  --memory-root  "$PWD/.e2e/memory" \
  --skills-root  "$PWD/.e2e/agents-home/skills"

That copies this package into <DSH_HOME>/profiles/memdev/node_modules/dsh-memory-forge and writes the loader row. Remove it with --uninstall.

Enable

Installing the bundle inserts this row into the profile patch:

- insert:
    - id: memory
      name: 'dsh-memory-forge'
      config:
        maxRecallItems: 4
        recallMinScore: 0.22

The row id stays memory, so overrides written for earlier versions keep working. With HMR enabled the plugin mounts immediately; otherwise restart the profile.

Configuration

All keys are optional. Values are validated at activation and every correction is logged.

KeyDefaultMeaning
memoryRoot$DSH_HOME/memoryRoot of the memory store.
skillsRoot$DSH_HOME/skillsRoot receiving forged SKILL.md bundles. Set it to $DSH_AGENTS_HOME/skills to share skills with other agent tools.
autoCapturetrueCapture conversation turns automatically.
captureAssistanttrueAlso capture the previous turn's assistant replies.
minCaptureChars24Shorter messages are not captured automatically.
maxCaptureChars4000Automatic capture truncates longer texts.
maxRecallItems4Memories injected per recall. 0 disables recall.
recallMinScore0.22Minimum relevance (0..1) to inject a memory.
recallMaxChars2000Character budget of the whole injected block.
halfLifeDays30Recency half-life; 0 disables recency weighting.
includeGlobalScopetrueRecall entries saved with scope: 'global'.
recallOnfirst-stepfirst-step or every-step.
debugfalseWrite <memoryRoot>/debug.log diagnostics.

Tools

ToolPurpose
memory_saveStore one durable fact, preference, decision, or lesson. scope: 'global' for cross-project preferences.
memory_searchRanked search over the workspace and global namespaces.
memory_forgetDelete a memory by id - preferred over writing a contradictory note.
memory_distill_skillWrite a SKILL.md bundle from a proven procedure, recording the source memory ids.

Tool descriptions carry the operating policy, so a session discovers when to save and recall without any prompt injection.

How it works

agent/pre-step (step 1)
  |- capture   user messages of this turn (from the decision's claimed batch)
  |            assistant messages of the previous turn (from the session log, seq-deduped)
  |- recall    query = newest user text
  |            rank(workspace + global) -> filter current-turn captures -> render block
  '- inject    append one `user` message with source kind `dsh-memory-forge`

Design decisions worth knowing:

  • The session log stays authoritative. Recall is a normal user message, so it replays, compacts, and survives resume. The memory store is a derived index, never a second log.
  • Capture is idempotent twice. Event sequence numbers prevent re-capture after resume; normalized-text dedupe prevents duplicates from repeated prompts.
  • Recall never echoes the current turn. A memory captured from this very turn is filtered out - it would restate what the model already has.
  • The plugin has no imports outside Node builtins. A Host bundle must load without a dependency tree, so schemas are hand-written and validated in place.
  • Forged skills are ordinary skill bundles. They land in a watched root, get parsed by @deepseek-ai/dsh-skill-filesystem, and appear in the next session's catalogue - no registry API, no restart.

Data layout

$DSH_HOME/memory/
  <workspace-key>/memories.jsonl     # sha256(cwd)[0:16]
  global/memories.jsonl              # cross-project memories
  debug.log                          # only with debug: true
$DSH_HOME/skills/<name>/SKILL.md     # forged skills

Each line is one JSON object:

{"id":"mem_mvtaup5t_c19e0b","text":"...","kind":"note","tags":["build"],"importance":1,
 "scope":"workspace","workspace":"4ae8d930ea1f76ea","createdAt":1792395281000,
 "sessionId":"session-...","seq":12,"turn":1,"source":"auto-capture"}

The store tolerates damaged lines (it skips them with a warning) and rewrites atomically on delete.

Verify

node --test                      # 62 unit tests: retrieval, store, rendering, tools, skills, config
node scripts/e2e.mjs --profile memdev   # 4 real headless turns against a mock provider

The offline end-to-end check runs actual harness turns with scripts/mock-provider.mjs, an Anthropic-Messages mock, and asserts from disk artifacts only:

  • A memory_save through the real tool pipeline writes the memory;
  • B a later turn receives the saved fact inside a recall block;
  • C memory_distill_skill writes a valid SKILL.md;
  • D the harness lists that skill in the next session's catalogue.

No API key is needed; the mock provider records every request body so assertions are made against what the model actually received.

The same four phases pass against the npm pack tarball installed with dsh plugin add file:<tgz>, which is the install path a registry package takes.

Limitations

  • Lexical retrieval only. BM25-style scoring handles identifiers, paths, and CJK bigrams well, but it will miss paraphrase-only matches that an embedding model would find.
  • No background summarization. Memories are conversation turns and explicit notes; there is no task-summary pipeline. DSH's compaction plugin already owns context compression.
  • Capture happens on the first step of a turn. A turn aborted during its first step may leave its user message stored without a reply; that is accurate, if occasionally noisy.
  • Subagent sessions are captured too. Delegated children run the same profile, so their turns enter the same workspace namespace. Disable autoCapture if that is unwanted.
  • One writer per file. Concurrent harness processes appending to the same namespace can interleave, but each JSONL line is written with a single appendFileSync, so lines stay intact. Delete rewrites through a temp file.
  • Skills are written, not curated. The plugin validates names and frontmatter, but deciding whether a procedure is worth keeping is the model's call.
  • No viewer. The files are plain JSONL; a UI plugin would be a separate package.

Roadmap

  • Optional embedding backend behind the same store interface.
  • A memory_stats tool and a compaction hook that expires superseded notes.
  • Web UI page listing, searching, and deleting memories.

Data and privacy

The plugin stores conversation text locally; SECURITY.md states exactly what is written, where it lives, what becomes model-visible, and how to delete it.

License

MIT. See LICENSE.