deepseekplugins

DeepSeek Harness plugin

dsh-message-gateway

Universal message-platform gateway for the DSH web GUI: configure QQ / WeChat / WeCom / WeCom AI bot / Discord / Telegram / WhatsApp / Email / Webhooks connectors, save credentials, test connections

Remote & Mobile
Jump to install

Source facts

Repository
a792883583/dsh-message-gateway
Latest update
Aug 22, 2026
Category
Remote & Mobile
GitHub stars
0
Format
plugin
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/a792883583/dsh-message-gateway
Plugin: dsh-message-gateway
Author: a792883583

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer5 files
README.en.mdSource · read only
README language

dsh-message-gateway

中文 · Español

A message-platform gateway plugin for the DSH Web GUI: a "Message platforms" entry below the "New session" button opens a full-screen manager for multi-platform message connectors — credential save, connection tests, status monitoring — plus a built-in persistent bridge for the WeCom AI bot: external messages drive the DSH assistant through a dedicated agent session, and replies stream back token by token.

Features

  • Sidebar entry: a "📮 Message platforms" button below "New session" opens the full-screen manager (close with ESC or by clicking the backdrop)
  • Multi-platform connectors: Telegram / Discord / QQ bot / WeCom / WeCom AI bot / WeChat (external Wechaty gateway) / WeChat Official Account / WhatsApp / Email / Webhooks

- Telegram bot: save a Bot Token to enable long polling instantly; chat with the bot directly (streaming replies via send + progressive edit, same as web) - Discord bot: save a Bot Token to connect to the gateway (enable the MESSAGE CONTENT privileged intent in the developer portal); chat in channels or DMs - QQ bot: save appId + secret to connect to the open-platform gateway (channels/groups/DMs); passive replies + streaming edits - WeCom app: fill in CorpID/AgentID/Secret plus the callback Token/EncodingAESKey, configure the callback URL (/gateway/wecom/callback) in the admin console, and users who message the app get auto replies - WeChat Official Account: fill in AppID/Secret plus the callback Token, configure the server URL (/gateway/wechat-mp/callback) in the console, and followers who message get auto replies - WhatsApp: fill in Token + Phone Number ID, configure the webhook (/gateway/whatsapp/webhook) in the Meta console, and users who message get auto replies - Email: fill in IMAP (receiving, 993/143) + SMTP (replying, 465/587/25); messages are grouped into per-thread sessions and replies use Re: original subject

  • Credential management: plaintext is persisted only to ~/.dsh/gateway.json (mode 600, atomic write); /gateway/list never returns credential plaintext, only a configured flag
  • Secret redaction: message content written to logs / console is automatically masked for likely secrets (sk- prefixed keys, GitHub tokens, Bearer, password= assignments, PEM private keys, and other common patterns), so secrets in bot conversations never leak into log files
  • Connection tests: real per-platform checks — Telegram/Discord via Bot API, QQ via access_token, WeCom via gettoken, WeChat MP via cgi-bin/token, WhatsApp via Graph API, Email via IMAP TCP banner, WeCom AI bot via the official SDK long connection (authenticated = pass)
  • WeCom AI bot persistent bridge: official SDK WebSocket long connection with exponential backoff reconnect; incoming text messages are injected into an isolated dedicated agent session that wakes the DSH driver; replies stream back as chunks and finalize via response_url

- Group-chat @mention stripping: the leading @bot-name is removed before the assistant sees the message - Slash commands: /help / /time / /status (Chinese aliases: 帮助/菜单/时间/状态) - Enter-chat welcome: a welcome message is auto-replied when a user enters a single chat for the first time that day - Proactive send channel: POST /gateway/send ({"chatid": "...", "content": "..."}, single chat = userid, group chat = group id) sends markdown messages as the bot - Universal proactive push: POST /gateway/push ({"platform": "...", "target": "...", "content": "...", "title": "optional"}) pushes text to any platform target for task notifications / other plugins: - platform supports telegram (target = numeric chatId), discord (target = channelId), wecom-aibot (target = userid/group id), email (target = address, title becomes the subject) - QQ has no active push since 2025-04-21 (passive replies only); calling it returns a clear error - an unconnected platform returns bridge not connected - Message routing rules (plugin config routes): route messages by "platform + keyword prefix" to a specific agent preset (isolated session) with an optional dedicated model / skill. E.g. { id: "code", matchPlatform: "telegram", matchPrefix: "code ", agentPreset: "code" } makes code write a function on Telegram enter a code-preset session. First matching rule wins; unmatched messages use the default agent - Slash commands: /help / /time / /status / /stats (Chinese aliases: 帮助/菜单/时间/状态/统计); /stats shows per-bridge connection status and active chat count

  • Webhook receive endpoint: POST /gateway/webhook/in accepts messages from external systems (any of text / content / message), injects them into the dedicated agent session and returns the full reply synchronously; an optional HMAC-SHA256 signing secret validates requests (contract: [docs/webhooks.md](docs/webhooks.md))
  • WeChat personal accounts (optional external gateway): QR login and status polling against a local Wechaty HTTP gateway (contract: [docs/wechaty-gateway.md](docs/wechaty-gateway.md))
  • Multilingual: Chinese / English / Español, following the DSH Web UI language (Spanish browsers auto-switch); defaults to Simplified Chinese
  • Light / dark theme follows the DSH Web GUI

Usage

1. Open DSH Web (dsh web) and click the "Message platforms" button in the sidebar 2. Pick a platform on the left, fill in credentials on the right 3. Click Save: credentials are persisted and a connection test runs automatically, refreshing the status immediately 4. Click Test connection: tests the current form values without saving 5. Saving botId + secret for the WeCom AI bot establishes the persistent bridge right away; deleting the config disconnects it

Install

# From npm (generic plugin, usable by any DSH user)
dsh plugin --profile web add dsh-message-gateway

Restart dsh web — the "Message platforms" button appears below "New session" in the sidebar. Open the page, pick a platform, fill in credentials and click Save — for the WeCom AI bot, saving botId + secret establishes the persistent bridge immediately and you can chat with the bot in WeCom right away (same as web: per-chat sessions + automatic context compression).

Config

All options have defaults and the plugin works out of the box; tune them via dsh plugin config or the profile config file:

| Option | Type | Default | Description | | --- | --- | --- | --- | | botLocale | zh \| en | zh | Bot reply language | | maxChatAgents | number | 40 | Max chat sessions kept per bot; oldest is evicted beyond this | | autoStartWecom | boolean | true | Auto-connect the WeCom AI bot from saved credentials at startup | | groupReply | boolean | true | Reply to group messages (false = single chats only) |

Docs

  • [Architecture & extension guide](docs/architecture.md) (how to add a platform connector)
  • [Webhook receive endpoint contract](docs/webhooks.md)
  • [WeChat (Wechaty) HTTP gateway contract](docs/wechaty-gateway.md)

Architecture

  • Host half (lib/index.js): /gateway/* routes (list / save / delete / test / wechat-status) + BridgeManager (agent session injection and event-stream polling) + WecomBridge (SDK long-connection lifecycle) + gateway-store (credential persistence)
  • Client half (lib/client.js): sidebar button mount + full-screen platform manager (React, loaded via the __ModuleLoader__ closure)

Feedback

Found a bug or have a feature request? Open an issue on GitHub Issues — your feedback helps us make the plugin better.

License

MIT

Back to searchOpen GitHub repository

More related plugins

View category