dsh-telegram-bridge

Your DSH sub-agent runs on a server, yet you want to ask it a question mid-commute without opening a terminal. dsh-telegram-bridge plugs a Telegram chat directly into a DSH sub-agent: send a message, the agent processes it, the reply lands back in the same conversation. A single install_telegram_bridge call registers and starts everything.

The bridge covers the full daily loop: long-polling the Bot API to receive and send messages; a typing indicator plus an editable Processing bubble with elapsed time while the agent thinks; a /model command with an inline-keyboard provider-and-model picker; /new for a fresh conversation, /reset to clear context, and /status for bridge health, all registered via setMyCommands so they appear in the Telegram slash-suggestion menu. A .tg-bridge-diag.json file persists in the host directory, giving you an out-of-process view of poll cycles, errors, and the resolved sandbox policy.

It is tuned for personal bots: roughly one poll cycle every 3 to 6 seconds, with occasional stalls up to 30 seconds on flaky networks. That pace suits single-chat conversations but not high-throughput fan-out. Because the HTTPS transport shells out to pwsh Invoke-WebRequest, the host sandbox policy must resolve to danger-full-access or equivalent; the default workspace-write policy blocks the TLS handshake to api.telegram.org. The dynamic plugin lives in process memory, so a DSH restart requires re-running the install tool to bring the bridge back up.