dsh-im-gateway

If you find yourself ping-ponging between WeChat, QQ, email, and Feishu while wishing you could just ask an AI agent for help without opening a browser, dsh-im-gateway is built for that moment. It bridges six external IM channels — WeChat ilink bot, QQ official bot, SMTP/IMAP email, China Mobile 5G messaging, Feishu official SDK, and a generic HTTP callback — into DeepSeek Harness, routing every incoming message into a persistent Agent session that carries context across turns while keeping separate chats and channels fully isolated.

The plugin is designed around three stages: inbound reception, agent bridging, and outbound delivery. Replies are claimed from the global session-event stream by rpcId so concurrent turns never overwrite each other; sessions survive process restarts without re-creation; and each channel carries its own working directory and model routing so two channels of the same type can never share an agent even if their external chat IDs collide. Built-in safeguards include sender allowlisting, five-second inbound de-duplication, per-session serialization, IM-side approval and user-question push-back, and honest connection-state reporting so a channel that says connected actually answers.

It is aimed at operators, teams, and solo developers who already run agents on DeepSeek Harness and want to extend the conversational surface into the IM apps they use every day — whether that means an email auto-triage assistant, a 5G-message knowledge base query, or a Feishu bot that triggers long-running inference.