bailinghub/bailinghub-dsh-plugin
通过DeepSeek Harness提交并跟踪受治理的业务任务,经由操作员配置的BailingHub路由进行。
Project Overview项目介绍
This is a native DeepSeek Harness plugin that enables the DSH agent to interact with business systems connected to BailingHub, following the existing approval rules to query records and update allowed business fields. It supports binding multiple authorizations from different systems in a single conversation, allowing flexible cross-system business operations. To install the plugin, you need Node.js 22.19.0+ or 24+, pnpm, and a compatible DSH release, and run the command dsh plugin --profile web add dsh-bailinghub@0.6.0 to get it set up. The matched release set for this version is BailingHub Core 0.8.0, SDK 0.6.0, and DSH 0.6.0.
After installation, business administrators first connect their company's internal business system to BailingHub and generate the required four public connection values for end users. Before sending the first message in a new conversation, users run slash commands to select the specific business scope they need for that conversation. Once the scope is confirmed by the plugin, users can ask the DSH agent to perform business operations using the permissions of the selected authorized accounts. No credentials are exposed to the agent, and all actions are automatically audited and logged by BailingHub for compliance tracking.
The plugin is released under the open source MIT license, and automatically installs the matched version of the bailinghub-mcp-server dependency during the initial installation process. It does not require users to store any sensitive information like business passwords, client tokens, or signing secrets in the plugin settings or chat conversation. Legacy versions of this plugin are still available for older integration paths, but existing users should follow the official migration guide to upgrade to the latest supported version. Custom self-hosted DSH hosts need to implement specific APIs for scope selection and session recovery to work fully with this plugin.
这是一个专为DeepSeek Harness开发的原生插件,用于对接BailingHub托管的业务系统,允许AI代理按照业务系统现有的审批规则执行操作,支持查询业务记录、更新授权字段,完成各类审批流程下的业务自动化任务。该插件支持在同一个对话中绑定多个不同系统的授权,方便完成跨系统的业务操作需求。
本插件面向需要将AI代理接入自有审批业务系统的企业用户,企业管理员需要先将业务系统接入BailingHub,再给终端用户配置公共连接信息。用户安装插件后,需要在新对话发送第一条消息前,通过斜杠命令选择本次对话要使用的业务授权范围,之后就可以让AI代理执行对应业务操作,所有操作都会留痕记录。
本插件遵循MIT许可证开源,要求使用Node.js 22.19.0+或24+版本,配合pnpm包管理器和对应版本的DeepSeek Harness使用,安装时会自动安装匹配版本的BailingHub MCP服务依赖。不建议在插件配置或对话中存放业务密码、客户端令牌等敏感信息。
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】,检查通过再动手。
插件:bailinghub-dsh-plugin(bailinghub/bailinghub-dsh-plugin)
仓库:https://github.com/bailinghub/bailinghub-dsh-plugin
本站详情页:https://www.yhbd.top/plugins/bailinghub-bailinghub-dsh-plugin/
本站登记:类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 2 · 最近提交 2026-09-24 · 主语言 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 更稳。
- 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 dsh-bailinghub@0.7.0
把 bailinghub/bailinghub-dsh-plugin 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
BailingHub for DeepSeek Harness
0.7.0: optional model services and plan billing
Keep orchestration local while Core relays model requests and meters shared allowance asynchronously. Discover chat models and image tools separately; preserve business authorization, approvals and audit. Pair Core 0.9.0 / SDK 0.7.0 / DSH 0.7.0.
简体中文 | English
Ask your local DeepSeek Harness Agent to work with a business system connected to BailingHub: find records, update allowed fields, and follow the system's existing approval rules. BailingHub records which authorization was used and what each business action returned.
Version 0.5.0 lets one conversation use authorizations from different systems on the same Hub. Authorize a shop and inventory system separately, select both for a new conversation and ask:
Check tumbler stock. If any are available, change the corresponding shop product's price to 59 and list it; otherwise leave it unlisted.
The Agent reads stock with the inventory authorization, then uses the shop authorization for the permitted price and listing actions. Those capabilities must already exist, and the product mapping must be confirmed. A stock read does not reserve or synchronize stock. Price changes, listing results and approvals are tracked separately.
The 0.4.0 same-system flow remains available: select Store A and Store B to compare sales without switching a global connection. New system descriptions explain each selected system's purpose before tool search, and business-supplied names identify the approved organization, account or other subject. See what changed and how to upgrade.
It also keeps the visible conversation together with links to its business actions. If uploading that record fails, it can retry after reconnecting or restarting without repeating those actions.
This is an independent community integration, not a plugin developed, certified, endorsed, or recommended by DeepSeek.
Install and start
You need Node.js 22.19.0+ or 24+, pnpm, and a compatible DeepSeek Harness release. Your
administrator must first connect the business system to BailingHub. The matched release set is
BailingHub Core 0.9.0 → BailingHub MCP/SDK 0.7.0 → this plugin 0.7.0.
Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要,完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →
Minglink/dsh-infinite-gen-4
kenryu42/cc-safety-net
hyhmrright/brooks-lint
toby-bridges/api-relay-audit
hashgraph-online/hol-guard
SeaOf0/dsh-redteam-model
howmp/dsh-pentest
saya-ch/dsh-mobile