cmfok/dsh-feishucard
DeepSeek Harness <-> 飞书(Lark)桥接,支持流式回复卡片 / 自研 DSH 飞书桥:长连接 + 流式回复卡片(工具面板/状态符号/限流熔断兜底)
Project Overview项目介绍
This is a natively built plugin specifically for DeepSeek Harness (DSH) that creates a bridge between Feishu (Lark) bot chats and DSH agent sessions. It uses the official Feishu SDK with long-lived WebSocket connections, eliminating the need for public IP addresses, domain names, or tunneling services to expose local endpoints. Each Feishu chat gets its own dedicated DSH agent session that never shares context with DSH's GUI sessions, and sessions persist across DSH restarts so context is never lost. It also supports common slash commands like /new, /switch, /list, and /help directly from within Feishu chats.
Installation is straightforward for DSH users: you can add it via the DSH plugin CLI using either a local directory path or the file: protocol. Configuration is stored separately from the codebase at ~/.dsh-feishucard/feishu.config.json, where you can define multiple bots each linked to their own workspace. If you are migrating from a legacy DSH Feishu plugin, the plugin will automatically copy your old configuration from the legacy ~/.cc-connect/ path on first boot, so no manual migration steps are needed.
The plugin is released under the open-source MIT license, so it is free to use, modify, and distribute. For developers working on the plugin, you can install dependencies with npm i, run a syntax check with npm run check, and execute end-to-end smoke tests with npm run smoke. The smoke test mocks both the DSH context and Feishu API to validate the full request lifecycle from inbound message to outbound streaming card. There are several known deployment pitfalls to note, so always verify your environment variables and API key before launching.
这是专为DeepSeek Harness(DSH)开发的原生插件,作用是将飞书(Lark)机器人接入DSH的Agent会话。它采用飞书官方SDK长连接收发消息,不需要公网IP、域名或者内网穿透隧道。每个飞书聊天拥有独立专属的Agent会话,支持/new /switch /list /help等常用命令,还提供输入中表情回执和流式回复卡片功能。
它支持开箱即用,整合了主机插件、长连接辅助子进程和自动注册包补丁。配置独立存放在~/.dsh-feishucard/目录,首次启动如果检测到旧版飞书插件在~/.cc-connect/的配置,会自动完成一次迁移。不要同时安装该插件和其他DSH飞书插件,否则同一个飞书应用的长连接会互相冲突。
该插件采用MIT开源许可,免费可商用。开发阶段可以通过npm安装依赖,运行语法检查和冒烟测试,冒烟测试会模拟DSH环境和飞书API,覆盖完整的请求链路。它存在几个已知的开发和部署陷阱,修改代码后需要同步更新DSH配置目录中的副本,启动DSH时需要确保环境变量携带DEEPSEEK_API_KEY。
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】,检查通过再动手。
插件:dsh-feishucard(cmfok/dsh-feishucard)
仓库:https://github.com/cmfok/dsh-feishucard
本站详情页:https://www.yhbd.top/plugins/cmfok-dsh-feishucard/
本站登记:类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 3 · 最近提交 2026-10-03 · 主语言 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 3 stars - very few users, little community feedback星标只有 3,几乎没人在用,遇到问题缺少社区反馈
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-feishucard
把 cmfok/dsh-feishucard 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
dsh-feishucard — DSH ↔ Feishu Streaming Card Bridge
把飞书(Lark)机器人接入 DeepSeek Harness 的 Agent 会话——完全自研(非 fork)。官方 SDK 长连接收发(无需公网 IP/域名/隧道)、每聊天独立专属会话、/new /switch /list /help 命令、处理中表情回执,以及流式回复卡片:过程话语内联 + 工具调用折叠面板 + 限流/退避/熔断/文本兜底。
A self-developed (not a fork) bridge between Feishu (Lark) chats and DeepSeek Harness agent sessions: official-SDK long connection (no public URL needed), dedicated per-chat sessions, /new /switch /list /help commands, a typing reaction, and a streaming reply card — inline agent notes, collapsible tool-call panels with status symbols, and rate-limit / backoff / circuit-breaker / plain-text fallback reliability.
单包即用:Host 插件(桥接逻辑)+ helper 子进程(长连接)+ bundle 补丁(自动注册)。One package, three pieces: host plugin, long-connection helper subprocess, and an auto-registered bundle patch.
独立自研,不依赖任何第三方 DSH 飞书插件。配置独立存放于
~/.dsh-feishucard/;检测到旧生态路径(~/.cc-connect/)有配置时启动自动迁移一次。不要与其他 DSH 飞书插件同时安装(同一飞书 App 的 WS 长连接互踢)。 Fully independent. Config lives in~/.dsh-feishucard/; a legacy config found at~/.cc-connect/is auto-migrated once on boot. Do not install alongside other DSH Feishu plugins (two WS long connections on one app kick each other).
✅ 更正(2026-10-02 实测,推翻本文件 2026-08-15 / 2026-09-18 的旧结论):本机 DSH profile 里
~/.dsh/profiles/web/node_modules/dsh-feishucard是目录联接(Junction),直接指向本仓库 (Get-Item报LinkType: Junction、Target: <本仓库路径>)⇒ 改源码 = 改 profile 副本, 配合@deepseek-ai/dsh-hmr(0.2 起;0.1.x 时期为cordis-plugin-hmr)保存即热重载。 实证:2026-10-02 同一轮里连续 4 次保存,日志依次出现plugin apply #8 / #9 / #10 / #11, 每次的md5/bytes都与源码一致。 旧结论「实体副本、HMR 覆盖不到源码、必须 sync + 重启」在本机不成立,已作废。 若你的安装方式不是 Junction(例如file:物化出实体副本),npm run sync仍是正确兜底 —— 体检 + 备份 + 同步 + 哈希复验,--dry-run只体检(退出码非 0 = 副本与源码不一致)。 复验"线上跑的是哪一版":grep 'plugin apply' <dsh日志>,行内含v<版本> md5=<前8位> bytes=<大小>。Corrected 2026-10-02: on this machine the profile entry is a junction to this repo, so the HMR watcher and the running copy coincide — saving the source hot-reloads the plugin (verified:
plugin apply #8–#11on four consecutive saves). The older "copy, not symlink ⇒ sync + restart required" note is stale;npm run syncremains the correct fallback for non-junction installs.
Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要,完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →
xmanrui/dsh-im
tencent-connect/dsh-qqbot
flymysql/dsh-remote
whiteguo233/dsh-openbiliclaw
omdsh-dev/dsh-lark
hanshanyike/dsh-yolo
THEWOLFWALKER/dsh-notifier