DSH Plugin HubDSH 插件市场

bonerush/dsh-obsidian-mem

Plugin插件 Native原生 ⭐ 3 MIT Memory & Knowledge记忆与知识库Docs & Writing文档与写作

DeepSeek Harness host plugin that keeps project documents and long-term memory as plain Markdown in a dedicated Obsidian vault.

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

dsh-obsidian-mem is a host plugin written specifically for DeepSeek Harness that stores a project's documents and long-term memory as plain Markdown inside a dedicated Obsidian vault. Installation starts with creating a local vault directory, then loading the GitHub repository through dsh plugin --; the plugin performs all writes while Obsidian only renders the result, so the editor never needs to be running. The codebase is deliberately split into a protocol layer and an adapter layer: the protocol uses the cross-agent SKILL.md convention and ships an MCP-style skill, while the DSH adapter exposes six mem_* tools, maintains an external node:sqlite FTS5 index, and distills completed turns automatically.

A typical workflow begins with a smoke test under a throwaway DSH_HOME created via mktemp -d, then graduates to the real home directory once verification passes. Each repository gets a stable projectId and a committed .obsidian-mem pointer, which maps to a fixed Projects/<slug>--<projectId first 8 hex> directory inside the vault containing index.md, Daily/, Docs/, Decisions/, Conventions/, Pitfalls/, Inbox/, and _meta/hot.md. The project also bundles a Codex CLI integration that reuses the same lib/ code through an MCP server, delivering identical recall briefs into a second harness. It targets developers who want plain local Markdown to remain the single source of truth while giving DSH sessions auditable, queryable memory.

Runtime dependencies are intentionally minimal: @deepseek-ai/schemastery for config validation, yaml for frontmatter, and Node's built-in node:sqlite so no native compilation is needed. Node must be at least 22.22.2 because earlier builds lack FTS5, and DSH must be 0.1.5-rc.2 or 0.1.7-rc.2 — the only versions actually verified, with results documented in docs/p0-compatibility.md and docs/smoke-results.md. The vault must live on local disk and should not be a personal vault the user already maintains, since the plugin writes project directories at the vault root. The package is released under MIT and published as git tags plus GitHub Releases, each carrying a dsh-obsidian-mem-<version>.tgz archive that the marketplace entry pins by tag to avoid latest-resolution link rot.

dsh-obsidian-mem 是一款为 DeepSeek Harness 专门编写的宿主插件，把项目文档与长期记忆以纯 Markdown 形式落地到一个独立的 Obsidian 仓库中。安装时先新建本地 vault 目录，然后通过 dsh plugin -- 加载 github 仓库；插件写入 vault，Obsidian 仅作阅读器使用，无需保持运行。代码库遵循"协议+适配器"分层：协议部分采用 Agent Skills 格式的 SKILL.md，可被复用；DSH 适配器层暴露六个 mem_* 工具，并维护一份位于 vault 之外的 node:sqlite FTS5 索引，在每个回合结束后自动蒸馏写入。

典型使用流程是先在临时 DSH_HOME 下做冒烟测试，确认通过后再切换到真实配置；每个仓库固定一个 projectId 与一个指针文件 .obsidian-mem，vault 内对应一个 Projects/<slug>--<id前8位> 目录，划分为 index.md、Daily/、Docs/、Decisions/、Conventions/、Pitfalls/、Inbox/ 和 _meta/hot.md 等区域。该项目同时附带一份 Codex CLI 集成，通过 MCP 服务复用 lib/，将同一套检索简报投递到第二套宿主。它面向希望以本地 Markdown 为唯一事实来源、且让 DSH 会话具备可审阅长期记忆的开发者。

运行时依赖仅有 @deepseek-ai/schemastery、yaml 以及 Node 自带的 node:sqlite，要求 Node ≥ 22.22.2（实测 22.13.0 缺少 FTS5），DSH 版本需为 0.1.5-rc.2 或 0.1.7-rc.2。vault 必须放在本地磁盘，且不应与个人笔记库混用；插件虽拒绝写入不属于自己的文件，但独立 vault 才能彻底隔离风险。仓库以 MIT 协议发布，版本号仅通过 git tag 与 GitHub Release 推送，每个 Release 还附带 dsh-obsidian-mem-<version>.tgz 预打包产物，marketplace 入口按 tag 锁定该资产，避免 latest 解析造成链接腐烂。

View on GitHub在 GitHub 查看

Recommended强烈推荐 Send to your DSH发给你的 DSH 安装 
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-obsidian-mem（bonerush/dsh-obsidian-mem）
仓库：https://github.com/bonerush/dsh-obsidian-mem
本站详情页：https://www.yhbd.top/plugins/bonerush-dsh-obsidian-mem/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 3 · 最近提交 2026-09-29 · 主语言 JavaScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意
  • Only 3 stars - very few users, little community feedback星标只有 3，几乎没人在用，遇到问题缺少社区反馈
DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

  • DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
  • External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
  • Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

  • Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
  • Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
  • curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
  • Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
  • Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
  • Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装 

dsh plugin --profile web add github:bonerush/dsh-obsidian-mem

把 bonerush/dsh-obsidian-mem 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

47.8 KB · 缓存于 2026-10-02 22:09:17 · 47.8 KB

dsh-obsidian-mem

English | 中文

License: MIT Node >= 22.22.2 DSH plugin

A DeepSeek Harness host plugin that keeps a project's documents and long-term memory as plain Markdown in a dedicated Obsidian vault.

One repository gets one stable projectId, one committed pointer file and one fixed directory in the vault. The plugin writes there; Obsidian just shows you the result. Obsidian does not need to be running, and no part of the vault depends on DSH.

repository                                vault (~/Documents/dsh-memory)
├── .obsidian-mem   ───────────►          └── Projects/<slug>--<projectId 前8位>/
│     projectId, slug,                    ├── index.md                hub / MOC
│     displayName, schema: 1              ├── Docs/  Decisions/  Conventions/  Pitfalls/
└── src/ …                                ├── Daily/YYYY-MM-DD.md
                                          ├── Inbox/                  待分类
                                          └── _meta/hot.md            热记忆

Two layers, on purpose:

  • Protocol (vault layout, the .obsidian-mem pointer, note frontmatter, the distillation output contract) is plain Markdown and is not DSH-specific. The shipped skill skills/obsidian-mem/SKILL.md follows the Agent Skills format, so it works in another harness too — codex/ installs that protocol and the same six operations into Codex CLI, through an MCP server that reuses lib/ rather than copying it, plus hooks for the session brief and a small relevant-note map on each new user prompt.
  • Adapter is DSH-specific: six mem_* tools, a node:sqlite search index kept outside the vault, and automatic distillation of completed turns. The recall injection left that list: both harnesses compose it from the same buildBrief, and each delivers it through its own extension point.

Read Honest limits before you enable automatic writes. This plugin is careful about what it refuses, but it is young. What follows is what this release writes down, not a claim to be exhaustive; CHANGELOG.md keeps the running record of what has been verified and what has not.

When something misbehaves, the package can produce a report you attach to an Issue yourself: generate it, read the JSON, then attach it. See Diagnostic report for an Issue.

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 bonerush/dsh-obsidian-mem 的 README.md。 在 GitHub 查看原文 →

Related相关推荐

← 上一个 Prev dsh-model-extension 下一个 Next DeepSeek-Harness-Token-Free →