Introduction¶

In the DSH ecosystem, plugins can extend DSH’s entry points and capabilities. For agent developers, one common requirement is: the DSH session is already running, but the user might not be at their computer and wants to quickly check the workspace, create sessions, view task status, or even cancel the current task from their phone.

dsh-telegram-bot is a DSH plugin maintained by yuko0331, licensed under MIT. It provides a restricted remote entry point through Telegram private chats, allowing users to interact with DSH, view sessions and task status, and control the current DSH session to the extent allowed by the configuration.

What It Is¶

dsh-telegram-bot is positioned as a remote interface for using and viewing DeepSeek Harness through Telegram private chats.

It is not a group chat bot, nor is it a full mobile replacement for the DSH Web interface. It is more like a whitelist-restricted remote terminal entry point: it only accepts configured Telegram numeric User IDs, only supports private chats, only processes text messages, and interacts with DSH via long polling.

Core Features¶

Verified capabilities include:

• Chat with DSH and receive replies
• View workspaces and live sessions
• Create sessions in a specified workspace
• View running tasks
• Cancel the current task
• Only allow one designated Telegram user to operate

Several usage boundaries are critical:

• Only accepts private chats; does not support group chat control
• Only supports text messages and long polling
• Does not support group chats, voice, files, or button operations
• The plugin can only switch to and control sessions it created itself
• /tasks displays running DSH sessions and does not read the browser task board
• Telegram cannot replace user approval for sensitive tool operations
• After a plugin restart, sessions need to be re-selected

Installation¶

Install the plugin into the DSH Web profile:

dsh plugin --profile web add git+ssh://git@github.com/yuko0331/DSH-telegram.git

Before installation, it is recommended to review the source code, behavior documentation, and MIT license in the GitHub repository. It operates with the permissions of the current dsh process, so command capabilities, session control, and task cancellation should be used in an environment you trust.

Configuration¶

Before enabling, you need two things: a Bot Token and an administrator numeric User ID.

1. Contact @BotFather on Telegram, run /newbot to create a bot, and obtain the Bot Token.
2. Use bots like @userinfobot to query your Telegram numeric User ID, for example, 123456789.
3. Open DSH’s settings page:

Settings → Telegram

4. Fill in the Bot Token and the administrator numeric User ID.
5. Enable “Telegram Bot.”
6. Save and apply.

The Bot Token is read through DSH’s credential system and is not written into the plugin configuration. The Bot Token is only written to the DSH credential system; pages and APIs will not read or return the plaintext Token.

Do not send the Token in chats, and do not commit it to Git.

Typical Usage¶

After enabling, send commands to this Telegram Bot in a private chat:

Sending any other plain text will enter the current DSH session.

For first-time use, you can follow this order:

/workspaces
/new <workspace ID>
Hello, please check the current project status

First, view the workspaces, then create and select a session, and finally send plain text to enter the current DSH session.

Use Cases and Considerations¶

This plugin is suitable for scenarios where you need remote mobile viewing and control of a single-user DSH session, such as:

• Viewing which workspaces currently exist
• Creating a new session
• Viewing running DSH sessions
• Canceling the current task
• Continuing the current DSH conversation on your phone

It is not suitable as a group chat collaboration entry point, a file transfer channel, a voice interaction entry point, or as the final approval layer for sensitive tool operations. Sensitive operations should still be handled according to DSH’s own security mechanisms.

Additionally, after a plugin restart, sessions need to be re-selected; if you previously created and selected a session via /new, do not assume the context selection state persists after a restart.

Conclusion¶

dsh-telegram-bot adds a controlled Telegram private chat entry point to DSH: it only allows one designated user, only supports text messages, only handles private chat scenarios, and covers common operations such as conversation, workspaces, sessions, task status, and task cancellation.

If you need to remotely view and operate DSH sessions from your phone, you can start validating with this plugin; when using it, make sure you accept its boundaries regarding single-user, private chat, text messages, and session switching.

GitHub:

https://github.com/yuko0331/DSH-telegram