DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins

@vlln/dsh-loop

Loop

定时循环插件:/loop 命令 + loop 工具 + 活动状态条(官方 dock 槽)+ 设置页(工具暴露开关)

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add @vlln/dsh-loop@0.4.4
README兼容性版本

兼容性与来源证明

Loop 以 @vlln/dsh-loop 发布,当前版本为 0.4.4。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
web
发布来源
npm
Registry 更新时间
2026/10/30

版本

0.4.4stable
2026/10/30
0.4.3stable
2026/10/19
0.4.2stable
2026/10/15
查看其余 4 个版本收起版本
0.4.1stable
2026/9/9
0.4.0stable
2026/8/30
0.3.1stable
2026/8/22
0.3.0stable
2026/8/21

相关插件

正在加载相关插件…

最新版
0.4.4
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
62.6 kB
文件数
8
Surface
web
许可证
MIT
发布源
npm
GitHub
★ 7
周下载
0
最近提交
2026/10/30
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 productivity-workflow 分类下经过校验的插件。

Acp App@deepseek-ai/dsh-acp-appdsh ACP 配置文件包:基于 dsh-base 的仅限自动化的 JSON-RPC stdio 和进程生命周期管理Experimental Schedule Bundle@deepseek-ai/dsh-experimental-schedule-bundle为 Web 组合添加 Schedule、其任务页面和时间上下文的可选捆绑包Web All@linxin666/dsh-web-allDSH Web UI 全家桶聚合插件:一键安装全部功能插件(task-board / pet / web-ui-settings / skin-center / community-plugins / compat shim)。compat 桥接层已并入本包(src/client),无需独立 compat npm 包。Ab Ocrdsh-ab-ocr--- description: "外部 ocr 工具:逐页识别扫描的 PDF 或图像,仅在处理完最后一页后按顺序合并页面,并使用模型确定的标题级别保存为一个 Markdown 文档。" kind: "package-reference" ---

README

loop

中文 | English

Scheduled loop plugin: `/loop` command + `loop` tool (self-adjusting by the model) + active status bar on the chat page, with support for multiple concurrent loops

Delivers a prompt to the current agent at a fixed interval — ideal for polling, PR babysitting, and build-fix-test cycles. Aligned with Claude Code's /loop semantics, multiple loops can run concurrently in a single session. Delivered as an official bundle plugin (dsh.bundle + dshClient channel), 0 patch.

Preview

loop status bar (real run screenshot: multiple loops collapse into a count bar, expanding lists them one by one)

Features

Tool (registered via defineTool, the model can self-adjust on every turn):

ToolDescription
loopstart (start a new loop) / stop (stop a specific one or all) / status / list (list loops in the current session)

Commands (user side):

CommandDescription
/loop [interval] <prompt>Start a new loop (interval 5m/30s/1h/2d or a bare number = minutes; bare /loop uses the built-in maintenance prompt)
/loop listList all loops in the current session (with ids)
/loop stop <id> / /loop stopStop a specific loop / stop all

/loop replies (the command-palette title/description, list / usage / stop output) follow the UI language: the client half relays its active locale to the plugin, so they render in Chinese or English to match the interface. Headless runs with no client in sight keep English.

UI (dock slot above the input box on the chat page):

FeatureDescription
Active status barSingle loop: ● ⟳ looping · <prompt> · 5m · next in 23s; multiple loops collapse into a count bar "N loops running · expand", click to expand the list
/ menu rowTyping / in the composer shows the ⟳ icon at the left of the /loop row (same position and size as every other command row), with a localized title ("Loop" / "循环")

Settings

The plugin ships a settings card on Settings → Plugins → this bundle's page (official plugins.bundle.config slot, keyed by the bundle package name @vlln/dsh-loop; the settings namespace is dsh-loop, the id of the entry that exports the Config schema). Each tool gets its own row with an official-looking Switch:

SettingDefaultEffect
Whether to inject the loop tool into the modelonWhen off, the loop tool is not registered for agents: the model can no longer see or call it (tools.schemas has no loop). The /loop command (user side) and the status bar are unaffected.

The card fields are driven by the client LOOP_TOOL_FIELDS table, mirrored one-to-one by the Node-side tool definition table — adding a tool means adding one entry on each side, and the settings card grows a new switch row automatically.

Changes apply as soon as you save (the schema's leaves are marked .volatile(): the host commits in place without remounting the entry and emits loader/volatile-update) — the plugin re-reads the snapshot and registers/unregisters the affected tools on the fly, so new sessions pick it up without a restart. Tool schemas are resolved live at every session/prompt assembly (there is no per-session snapshot): in-flight sessions also see the change from their next turn, and turning a tool off drops it from tools.schemas immediately, so a model that called it earlier can no longer reach it (they can only reconcile that through the turn record). The /loop command (user side) and the status bar are unaffected.

Installation

Recommended: one-line install from npm (build artifacts ship in the package, no build triggered):

dsh plugin --profile web add @vlln/dsh-loop
# to track the latest commit instead: dsh plugin --profile web add "github:vlln/dsh-loop#main"

Or from a local directory (when you have the source): git clone, then cd dsh-loop && dsh plugin --profile web add ..

Compatibility

dsh versionStatus
0.2.0-rc.2✅ Verified (migrated against 0.2.0 on 2026-10-03; command surface re-checked 2026-10-15)
Other versions⚠️ Unverified — if the /loop menu row loses its icon and localized title after a dsh upgrade (the command itself still works), upstream renamed an internal client command-surface method and the plugin silently falls back to the official fallback look

After installing, restart web for it to take effect (bundles are composed at startup); afterwards you can disable/enable it from the "Plugins" panel on the settings page (takes effect at runtime + persisted).

Usage

# User side
/loop 5m check PRs on the deploy branch   # delivered every 5 minutes
/loop list                                # loop-1: every 5m — check PRs on the deploy branch
/loop stop loop-1                         # stop a specific one
/loop stop                                # stop all

# Model side (loop tool)
loop action=start prompt="fix flaky test" interval="2m"
loop action=status
loop action=stop loop_id="loop-2"

Loops live in the current harness process and disappear when the process exits (not persisted across restarts, consistent with Claude Code /loop).

Development

pnpm install
pnpm run build      # tsdown: Node half (lib/index.mjs) + client bundle (lib/client.js)
  • Node half: src/index.mjs (commands/tool/loops status route /plugins/dsh-loop/loops)
  • client: src/client/index.tsx (dock slot status bar)

License

MIT License (example plugin of the DSH ecosystem).