dsh-feishu
DeepSeek Harness (dsh) 的 Feishu (Lark) 即时通讯桥接
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:itr-del/dsh-feishu#e1051647ec6eeda78fecf57e4510e77546fc43d9Feishu 以 dsh-feishu 发布，当前版本为 0.2.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Pluggable cordis plugin wiring a Feishu self-built bot into a running DeepSeek Harness (dsh)
webprofile — installable viadsh plugin add.
┌────────┐ WS ┌──────────────┐ cordis ┌──────────┐ LLM ┌──────────┐
│ Feishu │ ──────> │ this plugin │ ──────────> │ dsh agent │ ────────> │ DeepSeek │
│ IM │ <────── │ │ <────────── │ │ <──────── │ │
└────────┘ API └──────────────┘ events └──────────┘ stream └──────────┘
dsh-feishu — DeepSeek Harness × Feishu IM bridge
feishu:<open_id>).<|DSML|...> tool-call markers from outbound text.ask_user_question payloads (with their options) are
rendered as plain chat text and the turn is unblocked immediately — otherwise the tool hangs
until the watchdog fires, because it only accepts answers from the dsh web browser client.npm install -g @deepseek-ai/dsh
dsh web --help
dsh plugin add dsh-feishu
This installs the plugin into ~/.dsh/profiles/web/node_modules/dsh-feishu and
patches cordis.patch.yml automatically.
Create a Custom App at https://open.feishu.cn/app and copy appId + appSecret.
Under Event Subscriptions (事件与回调):
im.message.receive_v1.Under Permissions (权限), grant:
im:messageim:message.p2p_msg (required for DMs)Publish a version (发布版本) — without this the bot cannot receive events. Wait ~2 minutes after publishing.
export DEEPSEEK_API_KEY="sk-..."
export FEISHU_APP_ID="cli_..."
export FEISHU_APP_SECRET="..."
dsh web
You should see in logs:
[feishu] WebSocket started (appId=cli_xxx)
[feishu] FeishuBridgeService initialized
DM the bot anything — the agent will reply in the same conversation.
| Variable | Required | Default | Notes |
|---|---|---|---|
DEEPSEEK_API_KEY | yes (LLM) | — | https://platform.deepseek.com |
DEEPSEEK_BASE_URL | no | https://api.deepseek.com | For proxies |
FEISHU_APP_ID | yes | — | cli_xxx from app console |
FEISHU_APP_SECRET | yes | — | From app console — never commit |
DSH_FEISHU_WATCHDOG_TIMEOUT_MS | no | 1800000 (30 min) | Force-cancel threshold for a stalled turn |
DSH_FEISHU_PROGRESS_AFTER_MS | no | 45000 | How long a turn runs before progress updates start |
DSH_FEISHU_PROGRESS_INTERVAL_MS | no | 30000 | Minimum gap between two progress updates |
im.message.receive_v1 → this plugin.feishu:<open_id>.agent.followup(userMessage).idle, plugin reads agent.session.events, strips
DSML noise, and posts the reply via larkClient.im.message.create(...).ask_user_question call is bridged to the chat (question + options) and the turn is
cancelled to unblock it; a turn running past the threshold gets its new assistant text
flushed as a "progress" message. Both share one seq cursor with the final reply, so no
text is ever sent twice.ask_user_question / exit_plan_mode only accept
answers from the dsh web client. Over IM the plugin renders the question as text and cancels
the turn, and injects an environment notice so the model prefers asking in prose.MIT.
itr-del — 13918029394@163.com
Built while integrating dsh with a self-hosted Feishu bot on Ubuntu 22.04.
📖 Open-sourcing story: PUBLISHING.md — how this repo got published and listed.
中文文档见 README.zh.md。