dsh-telegram-bridge

Running DSH agents has two classic pain points: the session finishes and you miss it, or a confirmation card pops up while you are away from the desk. dsh-telegram-bridge moves both scenarios into Telegram on your phone. When a session returns to idle, a structured notification arrives in your chat—sidebar title, session name, type, and a content summary—and replying to that same message resumes the conversation with zero browser hunting.

Confirmations and approvals share the same interaction model. An ask_user_question prompt arrives as a message with the question and options; you answer by replying with a number, free text, or custom: content. Sandbox permission approvals push the tool name and reason; a single /approve allow or /approve deny sets a session-level auto-approval policy so subsequent identical requests no longer interrupt you.

Message routing falls back through four layers: replying to a notification reaches its bound session (the mapping is persisted and survives restarts), a #sess: tag in the body targets a session directly, a single globally pending question is auto-matched, and keyword-based routing sends unrecognised messages to a calendar app or creates a fresh chat. The whole link uses getUpdates long polling, so no public URL or webhook is required, and all state—authorised chats, approval policies, message-to-session maps—lives in a local state.json. It is built for DSH users who live on their phone and would rather reply to a notification than type a session id.