ThreeBody6666/dsh-im-hub
30Last commit Aug 15, 2026
dsh-im-hub DSH plugin
dsh-im-hub allows you to chat with your DeepSeek Harness agent from Feishu (Lark), WeCom (WeChat Work), and Telegram. It supports per-chat agent sessions, whitelist access control, and idle reaping. No public endpoint is required for Feishu/Telegram (long connection/polling), while WeCom uses an HTTP callback.
How to install the dsh-im-hub DSH plugin
dsh plugin --profile im add dsh-im-hubCopying does not run this command. Review the repository and version before installing the dsh-im-hub DSH plugin.
dsh-im-hub DSH plugin data source
dsh-im-hub DSH plugin snapshot date: Aug 16, 2026
discovered
What the dsh-im-hub DSH plugin can do
- Multi-platform IM gateway supporting Feishu (Lark), WeCom, and Telegram
- Per-chat agent sessions with multi-turn context and serialized message handling
- Whitelist enforcement (allowedUserIds) on every adapter to restrict access
- Slack-style commands: /help, /reset, /status, /model
- Mock adapter for testing without real platform credentials
- Web GUI settings card for live configuration (v0.2.0+)
Where the dsh-im-hub DSH plugin fits
- Deploy a personal assistant reachable via Telegram for quick queries
- Integrate a team bot into WeCom for internal document retrieval or status checks
- Use Feishu to interact with an agent for project management and task updates
- Test the agent locally with the mock adapter before exposing to production
- Enable multi-platform access for a single agent across different messaging apps
Who the dsh-im-hub DSH plugin is for
- Developers who want to integrate DeepSeek Harness with popular IM platforms
- Teams that need to access their AI agents from work messaging apps like WeCom or Feishu
- Power users who prefer controlling their agent via chat commands from their phone
dsh-im-hub DSH plugin limitations
- WeCom requires a public HTTPS URL or tunnel; no long-connection mode available
- Plugin is in early development (v0.2.0+) and configuration may change
- Whitelist must be explicitly set in production; empty list allows anyone to drive the agent
- Only text messages are supported; media (images, files) are not handled
- Feishu/Lark long-connection mode is only available for self-built (enterprise) apps, not open apps
dsh-im-hub DSH plugin: from the repository README
Quoted from the ThreeBody6666/dsh-im-hub README, the upstream source of the dsh-im-hub DSH plugin. Copyright remains with the original authors.
**[English](README.md) | [简体中文](README.zh.md)** A multi-platform IM gateway plugin for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (dsh): connect your dsh agent to **Feishu (Lark)**, **WeCom (WeChat Work)**, and **Telegram**, and chat with it from the messaging apps you already use. > One agent per chat. Multi-turn context. Whitelist access control. Idle reaping. No public endpoint required (Feishu long connection / Telegram long polling; WeCom uses an HTTP callback). ## Highlights - **Feishu (Lark)** — official WebSocket long connection (`/callback/ws/endpoint` + protobuf frames, client-driven ping keepalive, 3s event ACK, message-id dedup), or webhook mode. No public URL needed for the default mode. The same adapter also serves the **international Lark** edition (`open.larksuite.com`) via `adapters.lark`. - **WeCom (WeChat Work)** — app message callback with full `WXBizMsgCrypt` AES-256-CBC decryption and SHA1 signature verification, plus active replies via the messaging API. - **Telegram** — Bot API long polling (`getUpdates`), automatic message splitting at the 4096-char limit. - **Mock adapter** — stdin + local HTTP endpoint for testing w
Read the full READMERepository license: MIT
dsh-im-hub DSH plugin questions
How do I configure the Telegram adapter?
Create a bot via @BotFather and get the token. Then set `adapters.telegram.enabled: true` and `adapters.telegram.token` in your profile's `cordis.patch.yml`. You can also configure it via the Web GUI settings card under Settings → Plugins → IM Gateway. Optionally set `allowedUserIds` to restrict access.
Does WeCom require a public URL?
Yes, WeCom uses an HTTP callback and requires a public HTTPS endpoint (or a tunnel like ngrok). Configure the callback URL in the WeCom admin console to point to `https://your-public-host/wecom` and set the Token and EncodingAESKey in the plugin config.
What commands are supported in chat?
The plugin supports Slack-style commands: `/help` shows help, `/reset` clears the conversation context, `/status` shows active chats/agents/adapters, and `/model` shows the current model selection. Just type them in the IM chat.
Can I use the plugin without a public URL?
For Feishu (Lark) and Telegram, no public URL is needed. Feishu uses WebSocket long connection, and Telegram uses long polling. For WeCom, a public HTTPS URL is required because it relies on HTTP callbacks.
How do I reset a conversation?
Type `/reset` in the chat where you want to clear the context. This disposes the current agent session and creates a fresh one on the next message. You can also restart the plugin to reset all conversations.