dsh-loop-brake

DSH PLUGIN开发与运行时

仓库 jwilson411/dsh-loop-brake

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

为 DeepSeek Harness 提供工具调用熔断:同一工具以完全相同参数连续重复调用达阈值时直接拒绝执行,并抛出 LOOP_BRAKE 错误,防止 Agent 陷入死循环空烧 token。

一句话选型结论

按资料字段整理

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

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

安装

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

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

  2. 2
    执行安装命令

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

  3. 3
    确认已挂载

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

  4. 4
    试跑并检查权限

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

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

能做什么

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

dsh-loop-brake:为 DeepSeek Harness 拦截重复工具调用的熔断插件

  • 相同工具与参数重复调用熔断
  • 基于 sha256 精确哈希匹配
  • 拒绝时抛出 LOOP_BRAKE 错误
  • maxRepeats 可配置阈值

上游标签

deepseek-harnessdsh-plugin

验证等级与安全审查

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

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

逐项检查结果

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 插件清单中已激活 方式:插件清单查询
— · 其它检查项
  • L4_0_SANDBOX 沙盒安装判定 方式:沙盒安装执行

风险详情

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

选择建议

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

值得选的地方

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

先想清楚的地方

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

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
插件验证等级安全审查星标兼容版本安装命令
dsh-loop-brake当前 L5 · 运行验证通过 低风险 0 0.2.0-rc.2 等 11 个 有
deepseek-harness L3 · 安装规范通过 低风险 24.6 万 未标注 无
rea L4 · 沙盒安装通过 低风险 2.6 万 0.1.1-rc.2 有
dsh-TUI L4 · 沙盒安装通过 中风险 4,292 0.1.7-rc.2 等 5 个 有
mirage L3 · 安装规范通过 低风险 3,681 未标注 无
dashi-taskboard L4 · 沙盒安装通过 低风险 3,311 0.1.1-rc.2 有

仓库档案

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

README 全文

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

dsh-loop-brake

A DeepSeek Harness function plugin: a circuit breaker for identical
tool calls
.

An agent gets stuck. It calls search with {"q":"weather"}, reads the result,
decides it needs to call search with {"q":"weather"}, and does. Nothing is
wrong with any single call, so nothing stops it, and the loop runs until a
budget, a turn limit, or a human notices.

This plugin notices on the third one.

LoopBrakeError: loop brake: tool "search" called 3 times in a row with identical
arguments (call 9f2c1a7b3e04…, limit 3); the call was denied before it ran.
Change the arguments, call a different tool, or stop.

The tool body does not run. The error carries code: 'LOOP_BRAKE', the count,
the limit, and twelve hex characters of the call hash, so the denial is legible
in a log without the arguments themselves being copied into one.

What it is not

This is not an LLM similarity judge. It is not embeddings, not a fuzzy match,
not a semantic "are these two calls basically the same" question put to a model,
not a workflow engine, and not a second agent loop watching the first one.
There is no model call anywhere in this package and no threshold to tune.

Exact hash match only. Two calls are the same call when

sha256(toolName + "\n" + canonicalJson(args))

produces the same digest, and are different calls otherwise. Canonicalization
sorts object keys at every nesting level and nothing else — so {"a":1,"b":2}
and {"b":2,"a":1} are one call, and {"q":"weather"} and {"q":"weather "}
are two.

That boundary is worth stating plainly, because it decides what this catches:

  • An agent repeating a call byte for byte — caught, on the Nth try.
  • An agent looping while a timestamp, a nonce, a page cursor, or a retry counter
    changes in its arguments — not caught. Every call hashes differently, and
    this plugin has no opinion about whether they mean the same thing.
  • An agent alternating between two calls forever — not caught. The counter
    is a consecutive-repeat streak, so A, B, A, B never reaches three of
    anything.

A brake that fired on "these look similar" would need a model to decide what
similar means, which is a model call in front of every tool call in the
composition, with a false-positive rate and a bill. The exact-match version
costs microseconds, cannot hallucinate, and is explainable to whoever reads the
denial at three in the morning. It catches the single most common shape of a
stuck agent and it is honest about the rest.

Install

dsh plugin --profile default add github:jwilson411/dsh-loop-brake

The installer reads dsh.bundle.patch from the package manifest and appends
this package to the profile's ordered bundle list. Its cordis.patch.yml
carries one insert row, id: loop-brake, with no config — the defaults.

Pin the tools package at 0.1.1-rc.2; that is the release candidate this
plugin is developed and tested against.

Configure

One knob, in the plugin's row in the composed patch:

- id: loop-brake
config:
maxRepeats: 5
Key Default Meaning
maxRepeats 3 Consecutive identical calls a session may make before the next one is denied. Counting includes the denied call, so at 3 two identical calls run and the third is refused.

Must be an integer of at least 1. An unusable value is rejected when the plugin
applies, not at the first call: a brake with different teeth than the one a
profile asked for is discovered, if ever, only when a loop is already burning
tokens. 1 denies every repeat immediately, including the first call of any
streak — a debugging setting rather than a deployment one.

The environment fallback DSH_LOOP_BRAKE_MAX_REPEATS is read only when the
config key is absent. The patch row is the deployment's stated intent, so it
wins over an ambient variable.

An id-targeted patch replaces the row's whole config rather than merging into
it, so an override must restate every field it means to keep.

Counting

Counts are per session, and per session the plugin keeps one current hash
and one count — a streak, not a histogram.

  • Call A, A → the streak is at 2.
  • Call B → the A streak is gone; B is at 1.
  • Call A → back to 1, not 3.

Two sessions never share a count: two agents legitimately making the same call
are not one agent looping. A session is the explicit sessionId a caller
passes, else the calling agent's id from the execution input, else default.

Memory does not grow with session length — one slot per session, not one entry
per distinct call ever made.

The error

error.code       // 'LOOP_BRAKE'
error.toolName   // 'search'
error.count      // 3 — which consecutive repeat this was, counting this call
error.maxRepeats // 3
error.hashPrefix // '9f2c1a7b3e04' — the first 12 hex characters, and no more
error.sessionId  // the session whose streak tripped
error.plugin     // 'dsh-loop-brake'

LoopBrakeError is thrown, not returned. A brake a caller can drive past by
ignoring a return value is not a brake, and the failure this exists to stop is
precisely the case where nobody is reading return values carefully.

The arguments are never put in the error. They are the thing most likely to hold
a path, a query, or a credential the caller passed in, and the error message is
the thing most likely to be logged, shown, or handed back to a model.

How it attaches

apply patches the injected tool registry in two places and returns the
LoopBrake instance, so a host that wants to inspect or reset it can.

  • ctx.tools.register is patched, so every definition registered for the
    lifetime of this fiber carries a braked execute. This is the mandatory path
    and the only one this plugin assumes exists.
  • ctx.tools.execute is patched when the runtime exposes it, which catches
    what the register patch cannot: a tool registered before this plugin
    applied.

One host call passing through both seams is counted once, keyed by its call
id. A pair of wrappers that both counted would bite at half the configured
limit.

Both patches are undone on dispose, so stopping or reloading the plugin leaves
the registry exactly as it was found — and forgets every streak, which is the
right default. A brake that remembered across a reload would deny the first call
of a fresh run for something the previous run did.

No tool is registered. This plugin adds nothing to the model's tool surface.
A brake the model can call is a brake it can be talked into arguing with, and
there is nothing a status tool could report that the denial does not already
say.

Using the library directly

The counting half is exported on its own for a host that owns its call sites:

import { LoopBrake, decorateTool, wrapExecute } from 'dsh-loop-brake/loop-brake'

const brake = new LoopBrake({ maxRepeats: 3 })

// Wrap one execute…
const guarded = wrapExecute(execute, brake, { tool: 'search', sessionId: 's1' })

// …or copy a whole definition with its execute braked.
const braked = decorateTool(definition, brake)

decorateTool returns a copy; the original definition is left alone. Also
exported: callHash, canonicalJson, hashPrefix, sessionKey,
normalizeMaxRepeats, resolveMaxRepeats, LoopBrakeError,
InvalidMaxRepeatsError.

Dependencies

None at runtime. The shipped source imports node:crypto and nothing else — it
opens no socket, reads no file, and spawns no process, all of which the test
suite asserts rather than promises. @deepseek-ai/cordis and
@deepseek-ai/dsh-tools are peer dependencies, provided by the harness.

Node >=22.14.0.

Tests

npm install
npm test

No network, no credentials, no model weights. CI runs the same suite on Node
22.x and 24.x.

License

MIT. Copyright (c) 2026 jwilson411.

常见问题

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

在 DSH 里执行 `dsh plugin --profile web add github:jwilson411/dsh-loop-brake` 即可。

dsh-loop-brake 的验证等级是什么意思?

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

dsh-loop-brake 安全吗?

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

dsh-loop-brake 装之前要先确认什么?

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

dsh-loop-brake 支持哪些 DSH 版本?

上游记录的兼容版本包括 0.2.0-rc.2、0.2.0-rc.1、0.1.7-rc.2、0.1.7-alpha.2、0.1.6-alpha.2、0.1.6-alpha.1、0.1.5-rc.2、0.1.3-alpha.2。版本较多,只列出前 8 个。

dsh-loop-brake 用的是什么许可证?

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

dsh-loop-brake 有哪些功能?

相同工具与参数重复调用熔断、基于 sha256 精确哈希匹配、拒绝时抛出 LOOP_BRAKE 错误、maxRepeats 可配置阈值。

这条记录的数据可靠吗?

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

开发与运行时
按星标排序,可作替代方案

rea

rea

L4 · 沙盒安装通过 2.6 万 星

dsh-TUI

dsh-TUI

Claude Code 风格全屏终端 UI:像素鲸鱼顶栏、实时工作状态行、思考流式展开。

L4 · 沙盒安装通过 4,292 星

mirage

mirage

把文件系统与 bash 提供者换成 mirage 虚拟工作区:文件工具与 shell 命令作用于挂载的资源(RAM、S3、Redis、Sla

L3 · 安装规范通过 3,681 星

dashi-taskboard

dashi-taskboard

把当前已安装并运行中的 Codex Taskboard 嵌入 DeepSeek Harness 侧边栏,并通过 Launcher 运行时描述

L4 · 沙盒安装通过 3,311 星

jwilson411 的其它插件

6 个

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