Areium/dsh-fail-logger

Name: Areium/dsh-fail-logger
Author: Areium

Plugin插件 Native原生 ⭐ 10 MIT Prompts & Skills提示词与技能

DeepSeek Harness（DSH）插件：自动记录所有执行模式（原生工具 / PTC run_code / 代码内嵌工具调用）的工具失败错因，去重、计数、确定性排序后沉淀进 skill 的机器维护实录区段——让 Agent 越用越少错。

Project Overview项目介绍

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

dsh-fail-logger is a native plugin built specifically for DeepSeek Harness, designed to automatically record tool call failures that occur during agent execution. It captures failures from both native tool mode and PTC Code mode, only logging failures that are explicitly marked with isError: true in the tool result. It processes the captured failures through normalization, deduplication, frequency counting, deterministic ranking, TTL-based pruning, and redaction before storing them in a machine-maintained section of the relevant skill. Non-zero exit codes that are not marked as explicit errors are not logged, per the plugin’s strict trigger conditions. This ensures only genuine execution failures are kept in the log.

The plugin operates as a pure observer, using the same session log event hook that the official DSH telemetry plugin uses. It does not inject any services or wrap runtime code, so it can never alter or interfere with the normal execution of the agent. It sorts failures by frequency, so the most common failure causes appear at the top of the log section, making them easily visible to the model in subsequent sessions. By default, it also injects a small set of always-on system prompt rules to help the model avoid common execution mistakes before they happen.

The plugin can be installed via multiple methods for DSH, including npm install, GitHub release tag install, or manual patching of your DSH profile’s cordis.patch.yml file. After installation, you just need to restart DSH for your target profile, and it works out of the box with zero required configuration. All configuration options are optional, and you can customize things like the log storage directory, maximum entries per category, TTL for old entries, extra redaction rules, and ignore patterns. It is released under the open source MIT license, and you can run a simple two-step smoke test to verify it is working correctly after installation.

dsh-fail-logger 是专为 DeepSeek Harness（DSH）开发的原生插件，核心功能是自动记录 DSH 代理运行过程中发生的工具调用失败事件。无论代理运行在原生工具模式还是 PTC 代码模式，只要工具运行结果被标记为错误，就会被记录到对应技能的机器维护分区中，经过归一化去重、频次计数、确定性排序、TTL过期修剪和敏感信息脱敏处理，整理后的失败记录会供后续会话加载该技能时供模型参考。

这个插件作为纯观察者，通过和官方遥测插件相同的会话日志钩子获取失败数据，不会注入服务、包装运行时，也不会影响代理的正常执行流程。它会按分类整理高频失败原因，将出现次数最多的失败排在前列，帮助模型在后续操作中避开同样的错误，逐步降低整体失败率。它还默认自带 Always-on 提示规则，帮助模型提前避免常见的执行错误。

安装可通过 npm 或 GitHub 标签完成，DSH 安装后重启对应配置文件即可开箱使用，所有配置项均为可选。插件采用 MIT 许可证开源，所有选项可自定义，包括日志目录、最大条目数、信息保留时间、脱敏规则、忽略列表等。用户还可以通过触发一个确定的失败来验证插件是否正常工作。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-fail-logger（Areium/dsh-fail-logger）
仓库：https://github.com/Areium/dsh-fail-logger
本站详情页：https://www.yhbd.top/plugins/areium-dsh-fail-logger/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 10 · 最近提交 2026-09-20 · 主语言 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 note1 项提示

10 stars - an early-stage project星标 10，属于早期项目

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 dsh-fail-logger

把 Areium/dsh-fail-logger 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

15.6 KB · 缓存于 2026-08-23 03:41:19 · 15.6 KB

中文 | English

dsh-fail-logger

An all-mode tool failure recorder for DeepSeek Harness: whether the agent runs in native mode or PTC (Code Mode), any tool failure is automatically written into the machine-maintained section of a skill — normalized-dedup, counted, deterministically ranked, TTL-pruned, and redacted — so the next session's model sees the most common failure causes when it loads the skill. Fail less over time.

Coverage matrix & trigger conditions

Execution mode	Failure source	Recorded as (kind / message)
Native tools (read/grep/write and third-party plugin tools…)	`tool/call` + `tool/result` (tool-result block isError=true)	`tool` / `[read] ENOENT: no such file …`
PTC `run_code` failures	`tool/result` (isError=true)	official kind (`exception`/`timeout`/`abort`/…) / raw message
Nested tool calls inside a code program (`tools.*` throwing)	`tool/code-dispatch` (isError=true)	`tool` / `[bash] exit code: 1`

Trigger condition: a failure is recorded only when the tool result is marked isError: true. A non-zero shell exit code does NOT trigger recording (e.g. exit 1 is presented as plain text [exit code: 1], not an error) — only genuinely thrown tool calls (read on a missing file, grep failure, run_code crash, …) enter the log.

The observation point is the session log (session/event) — the exact same hook the official telemetry plugin uses. Pure observer: no service injection, no runtime wrapping, can never affect execution.

Session failures (captured automatically)	Skill auto-log section

Legend — left: tool failures in a session are captured automatically; right: the causes accumulate in the skill's auto-log section (deduplicated, counted, ranked by frequency).

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

渲染基于仓库 Areium/dsh-fail-logger 的 README.md。在 GitHub 查看原文 →