deepseek-harness-dingtalk
用于 DeepSeek Harness 的 DingTalk Stream 文本、图片和文件频道桥接
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add deepseek-harness-dingtalk@0.1.5Deepseek Harness Dingtalk 以 deepseek-harness-dingtalk 发布，当前版本为 0.1.5。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A DeepSeek Harness channel powered by the official dingtalk-stream SDK. It uses Stream WebSocket delivery, so no public callback server is required; a Client ID and Client Secret are sufficient for an application robot.
downloadCode retrieval for images and files; ordinary files are safely stored in the Agent workspace/approve <code> and /reject <code> decisions for one-shot tool approvals/new, registered Harness slash commands, /bot-ping, /bot-help, /bot-image-test, /bot-file-test, /bot-status, /bot-cancelpnpm dsh plugin --profile web add github:sliverp/DeepSeek-harness-dingtalk
For a local checkout:
pnpm dsh plugin --profile web add /absolute/path/to/DeepSeek-harness-dingtalk
DINGTALK_CLIENT_ID and store the Client Secret under the Harness credential reference DINGTALK_CLIENT_SECRET.Environment injection is supported for development:
export DINGTALK_CLIENT_ID='ding_your-client-id'
export DINGTALK_CLIENT_SECRET='your-client-secret'
pnpm dsh --profile web
For durable use, put the Client ID in ~/.dsh/.env and store the Client Secret through the Harness credential settings surface. Never commit credentials.
- id: dingtalk-channel
name: deepseek-harness-dingtalk
config:
clientId: !!js process.env.DINGTALK_CLIENT_ID
clientSecretRef: DINGTALK_CLIENT_SECRET
cwd: !!js process.env.DSH_DINGTALK_CWD ?? process.cwd()
agentPreset: standard
Restrictive production example:
singlePolicy: allowlist
singleAllowFrom: [staff-id-1]
groupPolicy: allowlist
groupAllowChats: [conversation-id-1]
imageInputMode: auto
maxInboundFileBytes: 20971520
maxOutboundFileBytes: 20971520
approvalTimeoutMs: 240000
reconnectDelayMs: 1000
Policies accept open, allowlist, or disabled. Combine allowlists with least-privilege Harness tool and workspace permissions.
Connection and authentication run in the background. Missing or invalid DingTalk credentials leave this channel offline and are logged without blocking Harness startup. The official SDK's built-in reconnect can leave endpoint-discovery failures as unhandled promises, so the plugin disables that path and supervises retries at reconnectDelayMs (1,000 milliseconds by default). Temporary DNS, authentication-endpoint, or WebSocket failures keep DingTalk offline and retrying without terminating Harness.
When Harness requests tool approval, the plugin sends a requester-bound six-digit code to the originating conversation. Reply /approve <code> to allow that operation once or /reject <code> to deny it. Codes are one-shot, cannot cross conversations, bypass ordinary message capacity while the original turn waits, and fail closed on timeout, cancellation, send failure, or shutdown. approvalTimeoutMs must remain below responseTimeoutMs.
Send /bot-ping, /bot-image-test, and /bot-file-test. The bot should return pong, a blue diagnostic image, and a text file. Then send “What files do I have?” plus an image or ordinary file to verify tool, image, and file paths. Request an operation that needs approval and reply with the exact /approve <code> or /reject <code> shown; the same turn should continue or stop without using the Web approval panel.
To verify lifecycle isolation, temporarily make the DingTalk endpoint unreachable. The log should report supervised reconnect failures at reconnectDelayMs while Harness Web continues returning HTTP 200; DingTalk should reconnect on its own after network recovery.
Version 0.1.1 uses the new dingtalk-v2 session namespace. Existing dingtalk-v1 sessions are not deleted and remain in Harness persistence, but the channel no longer appends to those potentially polluted sessions. It starts with a clean v2 session instead. /new creates another durable session while retaining existing records.
sessionWebhook is used only for its originating reply; it is not logged, persisted, or exposed to the model.pnpm install
pnpm run check
pnpm pack
The repository uses PNPM 10.33.4. Plugin runtime requires Node.js >=22.19 and does not require PNPM 11.
Protocol, message, and media behavior were cross-checked against DingTalk's official DingTalk-Real-AI/dingtalk-openclaw-connector v0.8.24. MIT licensed.