Qing45/dsh-feishu-chat

Two-way Feishu (Lark) chat bridge for DeepSeek Harness over the official WebSocket long connection: messages route to the bound workspace's latest session and replies return automatically; bot credentials and workspace routing are configurable from the settings page.

A Feishu (Lark) bot bridge for DeepSeek Harness: send a message to your Feishu bot and your DSH agent answers, and the agent can push messages back with the feishu_send_message tool. Inbound messages arrive over the official WebSocket long connection (im.message.receive_v1) and are delegated to a subagent of the bound workspace's latest session, with the text reply sent back to the same chat automatically. The settings page connects the bot by App ID / App Secret with no config files to edit by hand, and lists every workspace the profile knows about (name + path + last activity) so you can retarget inbound messages to another workspace live, without restarting the harness. The long connection is in-process: protobuf pbbp2 frame decode, automatic ack, ping keep-alive, fragment merging (sum/seq) and reconnect with backoff, all torn down cleanly on stop or update.

Notifications & Integrations ★ 1 updated 2026-08-17
View on GitHub ↗

Install

dsh plugin --profile web add dsh-feishu-chat

README Install section quoted verbatim (the README labels the npm form "once published" and gives the GitHub alternative dsh plugin --profile web add github:Qing45/dsh-feishu-chat). Registry-verified live 2026-09-15: dsh-feishu-chat 0.1.0 (published 2026-08-17) with a matching repository field (github.com/Qing45/dsh-feishu-chat), so the npm form does resolve now. Then restart dsh web and open 设置 → 飞书: paste the App ID and App Secret from Feishu Open Platform, click 保存并重新连接, and pick the bound workspace from the list. The README notes credentials stay local in $DSH_HOME/feishu-bot/config.json and are never committed or uploaded.

Compatibility

Runs in a DSH web profile and needs a Feishu Open Platform app for the App ID / App Secret pair. The README labels it community third-party code and warns that installing it runs it with your own permissions — check the source before installing. Credentials persist locally under $DSH_HOME/feishu-bot/.

Details

Recent updates

The README documents features, the internal file layout and caveats rather than a release table; the registry version when checked on 2026-09-15 was 0.1.0.

FAQ

Do I have to edit config files?
No — the README says you install the plugin, open 设置 → 飞书, paste the App ID and App Secret and click 保存并重新连接, and the long connection comes up immediately.
Which session answers my Feishu messages?
Per the README, inbound messages are delegated to a subagent of the bound workspace's latest session, and you can switch the bound workspace live from the settings list without a restart.
Where are my credentials stored?
The README states credentials stay local in $DSH_HOME/feishu-bot/config.json and are never committed or uploaded.

Alternatives

117BS/dsh-perlica-ding · AbcdefgXW/dsh-msg-hub · AI-Galaxy-GPU/dsh-sound

More plugins in Notifications & Integrations

Browse more in Notifications & Integrations

Guides for Notifications & Integrations plugins