dsh-feishu-bridge

Your daily standups, approvals, and team chat all live in Feishu (Lark), yet your DeepSeek Harness Agent runs silently in a local terminal. Switching back and forth between a chat window and a CLI to copy-paste prompts and read responses breaks your flow. dsh-feishu-bridge removes that friction: it opens a bidirectional channel between Feishu and a locally running dsh web instance over a WebSocket long connection. Send a private message or @mention the bot in a group, and the text lands in the Agent instantly; replies, permission approvals, and follow-up questions flow right back into the same Feishu conversation. No public port, no tunneling service, no extra URL to maintain.

A few design choices are worth noting. In one-on-one chats each Feishu user is automatically bound to its own DSH session, so conversations never bleed into each other. In group chats the bot only responds to explicit @mentions, keeping the channel quiet. Long Agent responses are rendered as cardkit typewriter cards that type out character by character; if the cardkit permission scope is missing the bridge silently falls back to plain text. When the Agent requests a permission grant, a confirmation prompt appears in the Feishu thread—reply "approve" or "deny" and the decision is relayed. Numbered multi-choice questions are answered by typing the option number. Both the Feishu WebSocket and the DSH event stream reconnect automatically after a network blip, so a dropped connection does not require manual intervention.

Who is this for? Teams that run their daily collaboration in Feishu and rely on a DeepSeek Harness Agent for code analysis, task orchestration, or knowledge work will find this the lightest way to fold Agent interactions into the chat window they already use. The plugin does not alter DSH internals; it simply bridges Feishu and the local loopback API, making deployment a two-line config change and teardown as easy as uninstalling the bundle.