andiven/dsh-messaging
dsh-messaging is a multi-platform messaging plugin for DeepSeek Harness — one plugin, many IM platforms. A MessagePlatform abstraction with drop-in adapters covers Feishu, Telegram, Discord and WeCom; each platform declares 12 typed capabilities so the agent can query what is possible before acting, unsupported features auto-degrade with user-friendly bilingual warnings (Feishu gets plain text instead of Markdown), and messages are deduplicated with per-chat serial processing and exponential-backoff retries honoring Telegram retry_after / Feishu rate-limit codes. Assistant text is streamed into a buffer and sent as one complete message at turn/end. Prereqs are per platform: a Feishu self-built app with im:message permissions, a Telegram bot from @BotFather, a Discord application with the bot and Message Content intent, or a WeCom self-built app with Corp ID/Secret/AgentId.
Install
dsh plugin --profile web add github:andiven/dsh-messagingGitHub/source per README (README EN primary w/ zh edition). npm name dsh-messaging exists but its repository field points to EvenLRs/dsh-messaging — NOT claimed. Install per README: dsh plugin --profile web add github:andiven/dsh-messaging, then configure a platform row in cordis.patch.yml (platform + app credentials + autoConnect).
Compatibility
DeepSeek Harness profiles via the agent followup seam; Feishu (websocket long connection), Telegram, Discord (Message Content privileged intent), WeCom (callback URL for inbound); battle-tested in Hermes Agent 3+ months.
Details
- Repo: andiven/dsh-messaging
- Category: Other
- Stars: 0
- Version: GitHub main (andiven/dsh-messaging)
- Last push: 2026-08-14
- First seen: 2026-08-14
Recent updates
Known limitation: Feishu media send is not yet implemented and honestly reports false; Discord Gateway resume is best-effort.
FAQ
- Which platforms are supported?
- Feishu, Telegram, Discord and WeCom through one MessagePlatform abstraction; unsupported capabilities auto-degrade with warnings instead of failing.
- How are replies delivered?
- Assistant chunks are buffered until turn/end, then sent as one complete message via the platform's send API — with per-chat serialization and dedupe.
- What do I need to configure?
- A platform row in cordis.patch.yml: app credentials (Feishu app id/secret, Telegram bot token, Discord bot token, or WeCom Corp ID + Secret + AgentId) and autoConnect.
Alternatives
GengDaPeng/dsh-agent-message · happyren/dsh-agent-messaging · ben7am1n/dsh-telegram