dsh-channel-telegram

DSH agents have historically been confined to local ACP or web sessions, making them hard to reach while away from the desk. dsh-channel-telegram closes that gap with a thin Telegram Bot bridge: it long-polls getUpdates for private-chat messages, maps each chatId to a dedicated DSH agent session, and drives the conversation through the exact same agents.create / agent.followup / agent.whenIdle pipeline used by the ACP bridge. The plugin ships independently and requires no changes to the DSH codebase. Each chat gets its own session and a serial queue so long-running tasks never block the poller; replies longer than 4096 characters are auto-chunked while a typing indicator is sent in the interim. Built-in slash commands (/start, /help, /new, /status) give users a lightweight conversational control surface. Security relies on a chat-ID allowlist as the sole gate: unlisted private chats receive a rejection notice, and group or channel messages are silently ignored. This plugin is ideal for developers who want to invoke DSH agents from their phone on the go, and for ops teams looking to expose a scoped, read-heavy conversation endpoint under a low-permission preset or an isolated DSH profile. Known v1 limitations include no streaming output, no media handling, and in-memory session mapping that resets naturally after a restart.