wz-heng/dsh-feishu-bridge

Name: wz-heng/dsh-feishu-bridge
Author: wz-heng

Plugin插件 Native原生 ⭐ 4 MIT Approval & Security审批与安全 Notifications & Remote通知与远程

用于DeepSeek Harness（dsh）的故障关闭式飞书（Lark）频道桥接——与机器人聊天，接收代理操作回传。可选择启用人工介入的bash审批（允许/拒绝卡片，超时故障关闭），一键/pair入门，Webhook签名/时间戳/重放验证，每日最新SDK金丝雀检测。社区插件，非DeepSeek官方出品。

Project Overview项目介绍

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

This is a DSH-native Feishu (Lark) channel bridge plugin that connects DSH to Feishu’s bot platform. When a user messages the configured Feishu bot, the bridge triggers a DSH agent turn and sends the final response back to the Feishu chat. It includes production-grade security features like a fail-closed allowlist, one-time pairing nonces, per-chat verbosity settings, and support for both WebSocket and Webhook transport. A daily SDK canary test runs against the latest DSH SDK release to catch breaking changes quickly. It uses a capability detection shim to maintain compatibility across SDK updates.

To get started, users first clone the repository, create a Python 3.12 virtual environment, activate it, and install the project with the development extras. All credentials must be set as environment variables, never committed to version control. The fail-closed allowlist is required; with no user IDs configured, the bot will reject all incoming messages by default. After starting the bridge, users send a one-time pairing code from the bridge console to the bot in a private Feishu chat to get added to the allowlist immediately without needing a server restart. Only users on the allowlist can trigger agent runs and approve tool execution.

The project is released under the open-source MIT license, and it is an independent community project not affiliated with DeepSeek. It runs entirely through the public DSH Python SDK and does not require any forked or patched DSH core code. There are several intentional limitations to note: no incremental streaming responses, no persistent cross-restart sessions, support for text messages only, and one model configuration per bridge process. The test suite includes isolated unit tests that do not consume API quota, plus optional smoke tests that use the real SDK and require valid credentials to run. It also includes separate JavaScript tests for the plugin shell code.

这是DeepSeek Harness的飞书（Lark）渠道桥接原生插件，支持用户在飞书中向绑定的机器人发送消息，调用DSH代理执行任务，并将任务结果返回飞书聊天窗口。它内置默认拒绝的fail-closed安全白名单、一次性配对校验、每个聊天独立的会话详细程度设置，同时支持WebSocket和Webhook两种传输方式，通过每日自动化测试适配最新DSH SDK更新。

用户需要先克隆仓库创建Python虚拟环境，安装依赖后配置飞书应用凭证和DeepSeek API密钥，启动服务后通过飞书私聊发送控制台输出的一次性配对码完成授权。只有在白名单内的用户才能调用DSH代理，支持远程工具审批，可直接在飞书中允许或拒绝工具执行请求，适合需要远程管控DSH代理的团队使用。

本项目采用MIT许可，是独立社区项目，不依赖修改过的DSH核心代码，完全通过公共DSH Python SDK调用功能。它存在一些设计上的限制，比如不支持增量流式回复、会话重启后不保留历史状态、仅支持文本消息，每个进程仅支持一个模型配置，用户使用前需要了解这些限制。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

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

插件：dsh-feishu-bridge（wz-heng/dsh-feishu-bridge）
仓库：https://github.com/wz-heng/dsh-feishu-bridge
本站详情页：https://www.yhbd.top/plugins/wz-heng-dsh-feishu-bridge/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 4 · 最近提交 2026-09-08 · 主语言 Python

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【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 warning1 项注意

Only 4 stars - very few users, little community feedback星标只有 4，几乎没人在用，遇到问题缺少社区反馈

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 github:wz-heng/dsh-feishu-bridge

把 wz-heng/dsh-feishu-bridge 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

19.2 KB · 缓存于 2026-09-08 19:40:54 · 19.2 KB

dsh-feishu-bridge

English | 中文

The SDK canary runs daily against the latest deepseek-harness-sdk and lark-channel-sdk releases (not the pinned versions this repo ships), so a breaking upstream change gets caught within a day instead of silently bit-rotting.

A Feishu (Lark) channel bridge for DeepSeek Harness (dsh): message a Feishu bot, it runs a dsh agent turn, the reply comes back to the chat.

This is an independent community project. It is not built, maintained, or endorsed by DeepSeek. It drives dsh entirely through its public Python SDK (deepseek-harness-sdk) — a subprocess boundary, no forked/patched harness code.

What this is

A production-grade Feishu bot bridge: fail-closed allowlist, one-time card nonces, per-chat verbosity, sticky sessions, both ws and webhook transports.
The thin adapter that talks to deepseek-harness-sdk lives in one file, src/dsh_feishu_bridge/dsh_adapter.py, and the SDK version is pinned exactly — the harness is a v0.1 developer preview that documents breaking changes between releases. That same adapter also carries a small capability-detection shim (probes the installed SDK's actual DeepSeekHarnessConfig fields via inspect.signature, never a hardcoded version check) so the nightly SDK canary — which installs the latest pre-release unpinned — keeps passing across a breaking field rename instead of just going red; see docs/architecture.md "SDK compat".

Screenshots

Remote tool approval: bash wants to run, Allow / Deny right in Feishu

Approved — the command runs and the reply comes back

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

渲染基于仓库 wz-heng/dsh-feishu-bridge 的 README.md。在 GitHub 查看原文 →