seek://map/dsh-im-hub
dsh-im-hub
#im #gateway #multi-platform
TL;DR
One gateway for Feishu, WeCom and Telegram: Feishu over outbound WebSocket (no public URL or server required), WeCom with encrypted callbacks, and Telegram polling — each chat bound to its own agent session behind a whitelist.
Three IM kingdoms, one bridge — and the Feishu leg works without ever opening a public port.
Facts
- license
- MIT
- note
- 飞书走 WebSocket 长连接，无需公网端点
Key points
- Feishu via WebSocket long connection — no public URL needed
- WeCom AES-encrypted callbacks and Telegram long polling included
- Per-chat sessions, whitelist access, settings card in the Web GUI
FAQ
Do I need to expose a public endpoint?
No for Feishu (outbound WebSocket) and Telegram (long polling); WeCom callbacks follow its official pattern.
How are chats mapped to sessions?
Each chat binds to its own persistent agent session, managed from the settings card.
Can I restrict who can reach my agent?
Yes — whitelist access control is built in.
Official references