dsh-approval-notify

DSH PLUGIN通知与集成

仓库 sakuraboy9128-cmd/dsh-approval-notify

通知与集成 L5 · 运行验证通过 安全审查:低风险 可信度:金 可安装插件
安装这个插件

当 DeepSeek Harness 等待你审批工具调用时弹出桌面通知,点击即可把 DSH 窗口切到前台,避免错过审批而卡住任务。

一句话选型结论

按资料字段整理

dsh-approval-notify 是通知与集成类的 DSH 可安装插件,验证等级 L5 · 运行验证通过,安全审查为低风险,列出 5 项功能,有可直接复制的安装命令。验证通过不等于安全:插件会读写文件、执行命令或联网,装前先到仓库确认它做了什么;涉及密钥或系统权限的,建议先在隔离环境试装。

分类通知与集成 收录类型可安装插件 验证等级L5 · 运行验证通过 安全审查低风险
验证等级 L5 L5 · 运行验证通过
GitHub 星标 0 复刻 0 · 未关闭 issue 0
最近更新 2026-09-30 创建于 2026-09-30
README 8.9 KB 正文体量,越大说明说明书写得越细

安装

可安装插件
在 DSH 里执行,装完用 dsh plugin list 确认已挂上;标了 L4 / L5 的命令已在沙盒里真实跑通
dsh plugin --profile web add github:sakuraboy9128-cmd/dsh-approval-notify
  1. 1
    确认版本与运行环境

    兼容的 DSH 版本为 0.2.0-rc.2;版本不匹配时安装会报错。

  2. 2
    执行安装命令

    在 DSH 里执行上面的命令;多包仓库要注意区分具体子包名,别装错包。

  3. 3
    确认已挂载

    用 dsh plugin list 查看列表里是否出现这个插件,出现即挂载成功。

  4. 4
    试跑并检查权限

    加载后跑一个最小用例,确认它能正常工作;同时看它申请了哪些文件、命令或网络权限。

兼容 DSH 版本0.2.0-rc.2版本不匹配时安装会报错
Node.js 要求未标注来自仓库 package.json 的 engines 字段
前置依赖无需要同时安装的同级依赖
npm 包名未发布到 npm可用 npm view 查看包信息

能做什么

5 项功能
字段来自项目仓库与公开索引,中文说明由本站标注

dsh-approval-notify:DeepSeek Harness 的审批桌面提醒插件

  • 审批请求触发桌面通知
  • 点击通知聚焦 DSH 窗口
  • 相同请求去重抑制
  • 支持 Windows 提示与卡片
  • 通知不改变审批结果

适用场景

通知

上游标签

deepseek-harnessdsh-plugin

验证等级与安全审查

L5 · 运行验证通过
自动化流程结论,不是人工审核
验证等级L5 · 运行验证通过在 dsh 沙盒中完成安装与运行冒烟——装得上、跑得起来
安全审查低风险静态分析结论,未标注不代表已通过审查
仓库健康度活跃按仓库活跃度与最近更新时间给出
可信度金综合仓库活跃度与验证结果

上面的结论来自上游最近一次自动化验证(2026-10-09): 同一套检查会在插件发新版后重跑,页面显示的是最新一次的逐项结果。

逐项检查结果

L1 · 已找到 ✓ 通过
  • L1.0_DEFAULTED_FROM_L3 由 L3 推定 默认通过——L3 安装规范已通过(全库 L3 扫描策略)
L2 · 结构化 ✓ 通过
  • L2.0_DEFAULTED_FROM_L3 由 L3 推定 默认通过——L3 安装规范已通过(全库 L3 扫描策略)
L3 · 安装规范 ✓ 通过
  • L3.1_INSTALL_COMMAND_PARSED 安装命令已解析 方式:安装规范解析
  • L3.2_DSH_VERSION_DECLARED DSH 版本已声明 方式:DSH 版本声明
L4 · 安装已测 ✓ 通过
  • L4.1_INSTALL_EXECUTED_CONFINED 受限沙盒内执行安装 方式:沙盒安装执行
  • L4.2_INSTALL_SUCCESS 沙盒安装成功 方式:沙盒安装执行
  • L4.3_ARTIFACT_CONFIRMED 安装产物已确认 方式:沙盒安装执行
L5 · 运行已测 ✓ 通过
  • L5.1_INSTALL_PASSED_SANDBOXED 沙盒安装通过 方式:沙盒安装执行
  • L5.2_WEB_BOOT_READY Web 启动就绪 方式:Web 启动
  • L5.3_HTTP_SERVED HTTP 服务响应 方式:HTTP 请求
  • L5.4_PLUGIN_INVENTORY_ACTIVE 插件清单中已激活 方式:插件清单查询

风险详情

  • 审查结论 通过
  • 结论说明 vet 静态分析未发现可疑行为,判定为干净(clean)。
  • 风险计数 严重 0 / 高 0 / 中 0
  • 风险详情 未发现严重或警告级问题。

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 验证等级 L5:安装和运行都在沙盒里跑通过,装完能直接用的概率高。
  • 静态安全审查为低风险,没有发现明显可疑行为。
  • 有可直接复制的安装命令,不用自己翻文档找入口。
  • 标注了兼容的 DSH 版本(0.2.0-rc.2),按版本装不容易报错。
  • 列出了 5 项功能,能直接看出它解决什么问题。

先想清楚的地方

  • 没有声明 Node.js 版本要求,版本不匹配可能装不上。
  • 验证通过不等于安全:插件会读写文件、执行命令或联网,装前先到仓库确认它做了什么。

更适合

  • 需要在通知与集成场景里给 DSH 补能力的人。
  • 想装完就能用、不想自己排依赖的人。
  • 能接受在本地装依赖、愿意自己确认权限的人。

不太适合

  • 只使用 DSH 官方内置能力、不接受第三方插件的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
插件验证等级安全审查星标兼容版本安装命令
dsh-approval-notify当前 L5 · 运行验证通过 低风险 0 0.2.0-rc.2 有
treg L3 · 安装规范通过 低风险 4,976 未标注 无
dsh-purge 未做沙盒验证 未标注 3,412 未标注 有
dsh-im L5 · 运行验证通过 低风险 1,837 0.1.7-rc.2 等 10 个 有
dsh-dafeiyu L5 · 运行验证通过 低风险 425 0.1.7-rc.2 等 10 个 有
dsh-trading L3 · 安装规范通过 低风险 235 未标注 无

仓库档案

通知与集成
字段来自项目仓库与公开索引,中文说明由本站标注
作者 / 维护方sakuraboy9128-cmd仓库 dsh-approval-notify · 默认分支 main
分类通知与集成notify
收录类型可安装插件声明了 dsh.bundle、可用 dsh plugin add 安装的条目
开发语言JavaScript仓库主语言
许可证MIT商用或二次分发前请确认条款原文
星标 / 复刻 / issue0 / 0 / 0收录时的数值,非实时
创建 / 更新2026-09-30 · 2026-09-30最后推送 2026-09-30
本站收录2026-10-02首次进入本站目录的时间

README 全文

8.9 KB
作者原文,中文版优先;只做安全转义,不改内容

dsh-approval-notify

English | 中文

A DeepSeek Harness bundle that pops a desktop notification when DSH is waiting for your approval of a tool call, and brings the DSH window to the front when you click that notification.

The fallback card presenter, captured on Windows 11 while a toast was unavailable.

It covers every ask the approval service raises, including the asks produced by @deepseek-ai/dsh-experimental-auto-review under the ask approval policy — the case it was written for: Auto review denies a call, DSH asks you, and you are not looking at the window.

Notifications are a reminder, not a permission. The notification cannot approve anything; the decision still happens in the DSH UI, and the notification never changes an approval outcome.

What it does

  • Attaches one listener to the approval/request waterfall owned by @deepseek-ai/dsh-user-approval.
  • Renders a localized title and body from the request's own fields (toolName, displayReason, reason). Nothing is inferred: a request without a tool name is labelled as unknown rather than guessed.
  • Suppresses an exact repeat (same tool and same reason) inside a configurable window, so one request is never announced twice while distinct requests always are.
  • Presents it on Windows through a long-lived PowerShell helper: a WinRT toast when the process can raise one, otherwise an always-on-top notification card in the corner of the screen.
  • On click, restores and focuses the DSH window; if DSH is not running, it launches the configured executable instead, whose single-instance lock restores the existing window.
  • Never throws and never awaits its own I/O inside the approval waterfall: a notification problem cannot turn an approval into a fail-closed unavailable outcome, and the answerers are never delayed.

macOS (osascript) and Linux (notify-send) get a plain notification without the click-to-focus action.

Requirements

  • DSH with the approval service (@deepseek-ai/dsh-user-approval) mounted, which is the case in the shipped Desktop and Web profiles.
  • Windows 10/11 for the toast and card presenters. macOS/Linux work with osascript/notify-send present.
  • No npm dependencies. The bundle imports Node built-ins only.

Install

dsh plugin --profile  add /absolute/path/to/dsh-approval-notify

The CLI installs the package and appends this bundle's declared patch, so the approval-notify row becomes part of the profile. Restart DSH if the loader reports the change as restart-required. Replace ` with the profile whose approvals you want announced —desktop` is the profile that ships Auto review.

Verify the notification path before relying on it:

node bin/cli.mjs test        # present one test notification
node bin/cli.mjs doctor      # print every resolved input of the path
node bin/cli.mjs logs        # tail the plugin and helper logs

Configuration

The row's config accepts these fields. Defaults are shown; an unusable value falls back to its default and is written to the plugin log as a warning.

Field Default Meaning
enabled true false activates the bundle without notifying anything
mode auto auto = toast, then card. Also toast, popup, balloon, none
clickAction focus-dsh focus-dsh focuses or launches the DSH window; none does nothing
locale auto auto follows the host locale; or zh, en
title '' Custom title; empty selects the localized default
includeReason true Include the request's own reason in the body
maxBodyChars 220 Truncate title and body beyond this
dedupeWindowMs 4000 Suppress an identical tool + reason repeat inside this window; 0 disables it
appId '' WinRT toast AppUserModelID; empty tries DSH's own IDs, then Explorer's
dshExePath '' Executable used when no DSH window exists; empty auto-detects
windowTitleSuffix DeepSeek Harness Title suffix identifying the DSH window to focus
registerProtocol true Register the dsh-approval-notify:// handler so a toast click can focus DSH
popupTimeoutMs 12000 How long the card stays on screen; hovering pauses the countdown
helperIdleMs 900000 Stop the helper after this much inactivity
sound true Play the notification sound
dshExeCandidates [] Extra executable paths tried before the built-in ones

Example patch row:

- id: approval-notify
name: 'dsh-approval-notify'
config:
mode: popup
locale: zh
dedupeWindowMs: 10000

How the click-reaches-DSH part works

registerProtocol writes three values under HKCU\Software\Classes\dsh-approval-notify so Windows hands dsh-approval-notify://focus to the bundled helper script. Removing it is one command:

node bin/cli.mjs unregister-protocol

The card presenter does not need the protocol handler at all: the click is delivered to the helper process itself, which is why the card is the reliable path for click-to-focus.

Windows only lets a process raise a window when that process has just received user input, so focus is attempted on the click path and never in the background. The helper logs which strategy produced the result (setForegroundWindow, isForeground, or launched) into helper.log, which is what dsh-approval-notify logs prints.

Verified behaviour

Tested on Windows 11 (build 26100), DSH Desktop profile, Node 24:

Behaviour Result
approval/request listener receives a live ask and queues a notice verified — notified: tool=pwsh reason=displayReason.zh in plugin.log
Bundle activates in a running profile without a restart verified — hot-loaded into the desktop profile, activated: … presenter=windows in plugin.log
WinRT toast from the helper spawned by the DSH host verified working — toast sent with AppUserModelID "com.deepseek.dsh"
WinRT toast from a sandboxed child process rejected with 0x80073D54 (no package identity) for com.deepseek.dsh, ai.deepseek.dsh.desktop, Microsoft.Windows.Explorer, and the PowerShell AUMID
Card fallback after a rejected toast verified — on screen and clickable (assets/screenshot-popup.png)
Click focuses the DSH window verified — setForegroundWindow=True isForeground=True, logged from real clicks
Protocol handler registration verified — reg.exe exit codes 0, 0, 0
Hook wiring: prepended listener, next() passthrough, contained notifier failure verified by test/plugin.test.mjs
Unit tests 40 passing (node --test)

The toast is the primary path and it does work where the host allows it: package identity is decided by whoever starts the helper, so auto keeps the toast first and the card second, and records which one each notice took rather than assuming either.

The live ask above was a sandbox-escalation approval. Auto review's asks arrive on the same seam — its tools/pre-execute listener returns { kind: 'ask', reason, displayReason }, which the tools pipeline routes through ctx.approval.request() — so it is covered by the same listener, but it was not separately observed end-to-end here.

Not verified: the macOS and Linux presenters (no such host available), multiple monitors, and DSH running elevated while the helper does not.

Troubleshooting

Symptom Cause and fix
No notification at all The session's approval policy is never (the service rejects before any answerer, so nothing is asked), the bundle row is disabled, or mode is none. Check dsh-approval-notify logs.
Toast never appears, card always does Expected on hosts without package identity — 0x80073D54 in helper.log. Set mode: popup to skip the attempt.
Click does not focus DSH registerProtocol: false, or no window title ends with windowTitleSuffix. Set windowTitleSuffix to the suffix DSH uses in your language.
Wrong language Set locale explicitly; auto follows the host process locale.
Notification repeats Different reasons are different notices by design. Raise dedupeWindowMs to collapse near-duplicates.
Helper left running It exits when the host exits and after helperIdleMs. Force it with mode: none and restarting DSH.

Logs live in %TEMP%\dsh-approval-notify\ (plugin.log, helper.log). Set DSH_APPROVAL_NOTIFY_DIR to pin that directory when the host gives every process a different temporary directory.

Development

node --test        # 40 tests, no dependencies
node bin/cli.mjs test --mode popup --wait 20000

Layout: index.js (the Cordis plugin), lib/ (config, copy, gate, presenters, helper lifecycle), assets/notify-helper.ps1 (toast, card, balloon, and the protocol handler in one file), bin/cli.mjs, test/.

License

MIT — see LICENSE.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
dsh-approval-notify 怎么安装?

在 DSH 里执行 `dsh plugin --profile web add github:sakuraboy9128-cmd/dsh-approval-notify` 即可。

dsh-approval-notify 的验证等级是什么意思?

L5 · 运行验证通过。在 dsh 沙盒中完成安装与运行冒烟——装得上、跑得起来

dsh-approval-notify 安全吗?

低风险。vet 静态分析未发现可疑行为,判定为干净(clean)。

dsh-approval-notify 装之前要先确认什么?

先看它会读写哪些文件、执行哪些命令、连接哪些网络地址;验证等级只说明装得上、跑得起来,不等于安全。涉及密钥或系统权限的,建议先在隔离环境试装。

dsh-approval-notify 支持哪些 DSH 版本?

上游记录的兼容版本包括 0.2.0-rc.2。

dsh-approval-notify 用的是什么许可证?

上游标注为 MIT。商用或二次分发前请到仓库确认许可证原文。

dsh-approval-notify 有哪些功能?

审批请求触发桌面通知、点击通知聚焦 DSH 窗口、相同请求去重抑制、支持 Windows 提示与卡片、通知不改变审批结果。

这条记录的数据可靠吗?

本站按仓库名去重后合并整理,字段以作者仓库与 npm 元数据为准;安装命令、仓库地址与 README 保持原文,带 L4 / L5 标记的安装命令已在隔离沙盒里真实跑通。

同名或近似条目

3 条
不同作者的仓库分开列,请确认你要装的是哪一个
通知与集成
按星标排序,可作替代方案

treg

treg

Treg 是面向 Agent 工具的 OpenRouter,聚合 60 个提供商的 2896 个端点,按调用计费,统一令牌访问,无需注册各供

L3 · 安装规范通过 4,976 星

dsh-purge

dsh-purge

dsh-purge Community · DeepSeek Harness 社区维护版:宿主兼容、状态诊断、提示词管理、更新与本机备份回滚

未标注验证等级 3,412 星

dsh-im

dsh-im

将IM机器人接入DeepSeek Harness,支持飞书、微信、钉钉等九种渠道,通过扫码或凭据配置,统一管理多机器人连接。

L5 · 运行验证通过 1,837 星

dsh-dafeiyu

dsh-dafeiyu

DSH 大肥鱼是一款由 DeepSeek Harness 真实工作状态驱动的桌面伴侣插件,以始终置顶的透明窗口实时展示 Agent 的思考、

L5 · 运行验证通过 425 星

dsh-trading

dsh-trading

L3 · 安装规范通过 235 星

sakuraboy9128-cmd 的其它插件

1 个

插件的元信息来自作者仓库;分类、验证等级与安全结论的中文说明为中文整理,最近核验 2026-10-09。