dsh-tg-bridge

DSH Telegram bridge

English | [Русский](README.ru.md)

A [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (DSH)

plugin that gives every DSH session its own topic in a Telegram forum group.

You can follow and drive a session from DSH or from Telegram; both sides see

the same conversation.

• One session, one topic. Each root session gets a topic named

workspace · session title. It is renamed when DSH titles the session,

closed when you archive it, and reopened when you restore it.

• Both directions. Messages you type in DSH appear in the topic, with

their pictures as photos (several as an album). Text,

photos, files and voice messages you send in the topic go into the session

exactly like a message typed in the DSH composer.

• Agent output. Answers stream live into one message that is edited as the

model writes. Tool calls are collapsed into one expandable block per run of

tools. Long answers arrive as answer.md; images the agent embeds or

presents arrive as photos. While the agent works the topic shows "typing…";

when a turn ends, a notifying ✅ Done line arrives.

• Subagents. Subagents never create topics. Each one shows as a single

line in its parent's topic: "working, waiting for result ⏳", then

"done ✅" (or failed ❌ / cancelled ⏹).

• Approvals and questions. Approval requests and ask_user_question

prompts arrive with inline buttons. Telegram and the DSH GUI race: whichever

answers first wins, and the prompt on the other side is withdrawn; a

question answered in DSH shows the chosen answer in the topic. Approvals,

questions and the end-of-turn line mention (@) whoever sent the request

from Telegram, or the first allowed user for requests typed in DSH.

• Commands. /stop, /status, /diff, /compact, /model,

/permission and more in a session topic; /sessions, /workspaces and /new in General. Other DSH

slash commands work too.

• Pinned status card. The first message of each topic (workspace, path,

session id, model) is pinned.

• Settings page and composer link. Everything is configured on the

plugin's page in DSH. The DSH composer shows a Telegram link that opens

the current session's topic.

Requirements

• DeepSeek Harness with the plugin manager (desktop app or dsh web).
• Node.js 22 or newer (the one DSH runs on).
• A Telegram bot from [@BotFather](https://t.me/BotFather).
• A Telegram supergroup with Topics enabled.
• Optional: ffmpeg for voice messages.

Install

1. In DSH open Plugins → Add plugin and enter one of:

• github:Nergous/dsh-tg-bridge (latest from GitHub), or
• an absolute path to a local clone, for example /home/me/projects/dsh-tg-bridge.

2. Choose Enable now, then open Plugins → Telegram bridge.

The plugin has no build step and no dependencies. After changing host code

(index.js, lib/) restart DSH; client.js reloads in the open page.

Set up

1. Bot token. Create a bot with @BotFather (/newbot), paste the token on

the settings page and press Save token. The token is stored in DSH

credentials (DSH_TELEGRAM_BOT_TOKEN), never in configuration files. An

environment variable of the same name also works.

2. Group. Create a group, open its settings and enable Topics. Add

the bot and make it an administrator with Manage topics and

Pin messages.

3. Bind. Press Get bind code and send /bind in the group

within 10 minutes. The group is saved, and you are added to the allowed

users. Add more Telegram user ids on the settings page if others should be

able to write to sessions. Messages from anyone else, from bots and from

anonymous admins are ignored.

4. Press Test connection. It checks the token, the group, Topics, and the

bot's rights.

5. Write something in any DSH session. Its topic appears in the group.

Only one process may poll a bot. If DSH desktop and dsh web run at the same