DSH Plugin HubDSH 插件市场

starfishwrx/dsh-git-memory

Plugin插件 Native原生 ⭐ 2 MIT Memory & Knowledge记忆与知识库Dev Workflow开发与代码工作流Sessions & Context会话与上下文

基于Git的、可审阅的DeepSeek Harness长期上下文。

Project Overview项目介绍

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

dsh-git-memory is a pre-alpha native plugin built exclusively for DeepSeek Harness (DSH) that provides Git-backed, reviewable long-term session context for DSH developer workflows. It operates under the core design invariant that one controlled memory transaction equals one Git commit, which keeps accumulated memory local, diffable, reviewable, and revertible at all times. The current release is a compatibility spike that only validates DSH integration seams, and it does not yet support storing end-user long-term memory for production use. It ships with a valid DSH bundle manifest that allows it to be installed directly as a DSH plugin.

This plugin is intended for DSH users who want long-term session context retention without sacrificing traceability or the ability to review changes. Working features in the current spike include an installable DSH bundle with a valid manifest, dynamic context registration via DSH’s ctx.systemPrompt.context() endpoint, and metadata tracking of session events. It also includes a human-facing command /memory status and a read-only model tool memory_status, which currently only outputs aggregate event counts and timestamps stored in in-process memory. It never retains full message content or tool call results at this early stage of development.

The plugin is released under the open-source MIT license, and it has not yet been published to the npm registry. To install it from source, you will need Node.js 24 or newer, pnpm 11, and DeepSeek Harness version 0.1.0-rc.6. The standard install flow is to clone the repository, run pnpm install and pnpm verify, then add the plugin to your DSH web profile with dsh plugin --profile web add .. Because the package requires a build step when installed from GitHub, you will need to enable pnpm’s allowBuilds permission to complete the install. It is currently tested on Windows and Ubuntu via continuous integration.

这是一个面向DeepSeek Harness（DSH）的原生插件，当前处于预Alpha测试阶段，核心目标是为DSH提供Git后端、可审核的长期会话上下文。该项目遵循的核心设计原则是一次可控的记忆事务对应一次Git提交，让积累的记忆始终保持本地可存储、差异可对比、内容可审核和操作可回滚。当前版本是兼容性原型，仅验证了DSH集成链路，暂不支持存储用户实际记忆数据。

该插件面向需要长期保存开发会话上下文，同时对记忆内容的可追溯性和安全性有要求的DSH用户。目前可用功能包括可安装的DSH包、通过DSH的ctx.systemPrompt.context()接口注册动态上下文、记录会话元数据，同时提供了/memory status人类命令和memory_status只读模型工具。当前仅在进程内存中记录聚合事件计数和时间戳，不保留任何消息或工具调用内容。

该项目采用MIT许可证开源，从源码安装需要Node.js 24+、pnpm 11和DSH 0.1.0-rc.6版本，暂未发布到npm。安装步骤为克隆仓库后安装依赖，执行验证，再通过dsh plugin命令添加插件，需要开放pnpm的allowBuilds权限。当前仅支持Windows和Ubuntu平台，已配置CI进行持续测试。

View on GitHub在 GitHub 查看

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

插件：dsh-git-memory（starfishwrx/dsh-git-memory）
仓库：https://github.com/starfishwrx/dsh-git-memory
本站详情页：https://www.yhbd.top/plugins/starfishwrx-dsh-git-memory/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 2 · 最近提交 2026-08-15 · 主语言 TypeScript

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

【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 2 stars - very few users, little community feedback星标只有 2，几乎没人在用，遇到问题缺少社区反馈
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:starfishwrx/dsh-git-memory

把 starfishwrx/dsh-git-memory 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

4.2 KB · 缓存于 2026-08-26 05:39:03 · 4.2 KB

DSH Git Memory

CI License: MIT

Git-backed, reviewable long-term context for DeepSeek Harness.

Status: compatibility spike / pre-alpha. The current release proves the DSH integration seams and deliberately does not store user memory yet.

Product direction

DSH Git Memory is being built around one trust invariant:

One controlled memory transaction equals one Git commit.

The intended product gives DeepSeek Harness useful context on day one, then accumulates source-backed memory during normal use. Accepted memory stays local, diffable, reviewable, and revertible.

What works today

  • Installable DSH bundle with a dsh.bundle manifest.
  • Stable dynamic context registered through ctx.systemPrompt.context().
  • Metadata-only observation of session/event.
  • A direct human command: /memory status.
  • A read-only model tool: memory_status.
  • Windows and Ubuntu CI.
  • No transcript persistence, no background model calls, and no memory writes.

The spike records only aggregate event counts and timestamps in process memory. It never retains message or tool-result content.

Quick start from source

Prerequisites:

  • Node.js 24 or newer.
  • pnpm 11.
  • DeepSeek Harness 0.1.0-rc.6.
git clone https://github.com/starfishwrx/dsh-git-memory.git
cd dsh-git-memory
pnpm install
pnpm verify
dsh plugin --profile web add .
dsh --profile web --dump-config

Start the Web profile, then run:

/memory status

The model can also call:

memory_status

This package has not been published to npm yet. GitHub dependency installs run the package's prepare build and therefore require explicit pnpm allowBuilds permission. Pin a commit when testing a source install.

Planned user experience

  1. /memory setup gathers basic profile, project, goal, preference, boundary, and consent information.
  2. A confirmed onboarding draft becomes an auditable baseline commit.
  3. Normal DSH sessions generate bounded, redacted memory candidates.
  4. Review mode lets the user approve, edit, or reject candidates.
  5. Conservative automation can be enabled only after an initial trust period.
  6. DSH receives a bounded dynamic context snapshot; detailed recall uses memory_search.

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

渲染基于仓库 starfishwrx/dsh-git-memory 的 README.md。 在 GitHub 查看原文 →

Related相关推荐

← 上一个 Prev dsh-deepseek-usage 下一个 Next dsh-undo →