ben7am1n/dsh-telegram
Project Overview项目介绍
dsh-telegram is a native protocol driver plugin built exclusively for DeepSeek Harness that adapts the Telegram messaging platform to DSH agent sessions. To install the plugin, you can add it from a local path, a GitHub repository, or the npm registry once it is published. For example, installing from a GitHub source requires running pnpm dsh plugin --profile web add github:<you>/dsh-telegram, and pnpm ≥10 will require adding the package key to your profile's allowBuilds list first. After installation, you must configure your Telegram bot token and allowed user IDs in your DSH profile's cordis.patch.yml file before starting DSH. You can also set the bot token via the environment variable DSH_TELEGRAM_BOT_TOKEN instead of hardcoding it into the config file.
This plugin is designed for three primary groups of users: individuals who want to access their DSH agents from a mobile phone without opening the DSH web UI, teams that want a shared auditable chat interface for their agents that leverages Telegram's built-in history storage, and developers who want a minimal, readable reference for writing their own DSH protocol driver plugins. Once configured, you can start DSH, open your new Telegram bot chat, send /start to initialize a session, and then send any text query to your DSH agent. Each allowed chat gets its own dedicated agent session, and subsequent messages are added as followups to preserve full conversation history. Unauthorized users are immediately rejected with a warning message, and the plugin supports /new for a fresh session and /status to check current plugin status.
dsh-telegram requires Node.js version 22.19 or newer, as it relies on the global fetch API built into modern Node.js releases. It is currently built and verified against DSH version 0.1.0-rc.6 and Cordis version 4.0.1 or newer, with the last compatibility verification completed in August 2026. It has several known current limitations: it does not support webhook mode, does not handle rich messages like media or voice, and stores the chat-to-session mapping only in memory, so restarting DSH will erase all open active sessions. It is released under the open source MIT license, has zero runtime dependencies, and only communicates with the public Telegram Bot API at api.telegram.org.
dsh-telegram 是专为 DeepSeek Harness 开发的原生插件,作用是 Telegram 运行时适配器,让用户可以直接通过 Telegram 和自己的 DSH 代理交互。它使用长轮询方式对接 Telegram Bot API,不需要额外搭建服务器或配置 webhook,会为每个允许的聊天创建独立的 DSH 代理会话。Telegram 消息会通过 followup() 传入代理,代理生成的回复内容会流式返回,超过 4096 字符限制的长回复会自动分段。
这个插件适合想要在手机上随时查询 DSH 代理、不需要打开 DSH 网页界面的用户,也适合需要团队共享可审计对话记录的开发团队,还可作为 DSH 协议驱动插件开发的最小参考示例。用户安装后需要先通过 @BotFather 创建 Telegram 机器人,复制令牌,找到自己的 Telegram 用户 ID,再将二者配置到 DSH 配置文件中才可使用。
该插件要求 Node.js 版本不低于 22.19,适配 DSH 0.1.0-rc.6 和 cordis 4.0.1 以上版本,目前不支持 webhook 模式,也不支持富媒体消息,会话映射仅保存在内存中,重启 DSH 会丢失现有会话。它采用 MIT 许可,零运行时依赖,直接使用 Node.js 内置的 fetch 发起请求,仅和 api.telegram.org 通信,不会额外读写本地文件。
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】,检查通过再动手。
插件:dsh-telegram(ben7am1n/dsh-telegram)
仓库:https://github.com/ben7am1n/dsh-telegram
本站详情页:https://www.yhbd.top/plugins/ben7am1n-dsh-telegram/
本站登记:类型 plugin · 归类 原生 DSH 插件 · 许可证未声明 · ⭐ 3 · 最近提交 2026-08-13 · 主语言 TypeScript
按下面顺序执行,每步先把结论告诉我,再进入下一步:
【1 兼容性检查】
① 我这边:DSH 版本、Node 版本、操作系统、当前 profile(web / desktop)。
② 读它的 README、package.json、插件 manifest,列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对,结论只写「满足 / 不满足 / 未知」三种;不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突:命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。
【2 安全性检查】
① 仓库可信度:和上面「本站登记」是否一致;star / fork 数、创建时间、最近提交,是否归档或长期停更。
② 安装脚本:逐行看 package.json 的 preinstall / install / postinstall,以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名,立刻停下来告诉我,不要继续装。
③ 依赖:列出新增依赖,标出无人维护、或与知名包拼写近似的可疑包(typosquatting)。
④ 权限与副作用:它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限(filesystem / network / shell / clipboard 等),以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限,或权限明显超出功能所需,先停下来问我。
【3 安装】
上面两步没有「不满足」和「高危项」时才执行;用官方推荐方式安装,不要自行提权。
【4 汇报】
用表格输出:检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜,也不要替我决定。
Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH:它会先核对兼容性与安全性(逐条给「满足 / 不满足 / 未知」),确认没问题再安装,有高危项会停下来问你。框内可滚动,复制到的是完整提示词;安装命令不一定准确,发给 DSH 更稳。
- No license declared - all rights reserved by default; ask the author before commercial use or redistribution未声明开源许可证 —— 默认「保留所有权利」,商用或再分发前先问作者
- Only 3 stars - very few users, little community feedback星标只有 3,几乎没人在用,遇到问题缺少社区反馈
DSH walks through these 9 checksDSH 会逐条核对这 9 项
Compatibility兼容性
- DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
- External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时(Electron / Python / Docker 等)是否齐备
- Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突:命令名、skill / tool 重名、端口占用、重复 MCP 注册
Security安全性
- Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致,是否归档或长期停更
- Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
- curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
- Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
- Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需(filesystem / network / shell / clipboard)
- Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限,以及卸载与回滚方式
Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照,不能替代安全审计。
Or use CLI install (for developers)或使用命令行安装(适合开发者)
CLI Install命令行安装
dsh plugin --profile web add github:ben7am1n/dsh-telegram
把 ben7am1n/dsh-telegram 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
dsh-telegram
Telegram runtime adapter for DeepSeek Harness — talk to your dsh agents from Telegram. Every allowed chat maps to one agent session; messages flow in via followup(), committed assistant text streams back to the chat. Zero runtime dependencies (plain HTTP over Node's built-in fetch).
Overview
dsh-telegram turns a DeepSeek Harness agent into a Telegram bot. It is a protocol driver in the dsh extension model: it adapts an external wire peer (Telegram) to ctx.agents, the same role the official ACP/JSON-RPC bridges play — but for human chat instead of automation.
Who is it for?
- Anyone who wants to query their DeepSeek agents from a phone, without opening the web UI.
- Teams that want a shared, auditable chat surface in front of a harness (Telegram history is kept by Telegram).
- Developers who want a minimal, readable reference for writing a protocol-driver plugin.
What it does
- Long-polls the Telegram Bot API (
getUpdates) with no server, no webhook, no framework. - Creates one dsh agent session per allowed chat on first message; subsequent messages
followup()into the same session, so conversation history is preserved. - Streams every committed assistant message back to the chat; long replies are split at Telegram's 4096-char limit.
- Supports
/start,/new(fresh session),/status. - Rejects unauthorized users outright (configurable allowlist).
What it does not do (yet)
- No webhook mode (requires a public HTTPS endpoint).
- No inline keyboards, media, voice, or rich messages — text in, text out.
- No cross-restart persistence of chat→session mapping (see Compatibility).
Compatibility
- Requires Node.js ≥ 22.19 (uses global
fetch). - Built and verified against
@deepseek-ai/dsh@0.1.0-rc.6/@deepseek-ai/cordis@^4.0.1. - Last verified: 2026-08-13 against mainline commit of the same day (dsh repo
master). - dsh is in developer preview and iterates rapidly. Pin your dsh version and re-verify after updates; the plugin's peer dependencies (
@deepseek-ai/dsh-agent,dsh-llm,dsh-session) may change shape between RC releases. - Chat→session mapping lives in memory: restarting dsh loses open sessions (use
/newto start a fresh one).
Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要,完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →
xmanrui/dsh-im
tencent-connect/dsh-qqbot
flymysql/dsh-remote
whiteguo233/dsh-openbiliclaw
omdsh-dev/dsh-lark
hanshanyike/dsh-yolo
THEWOLFWALKER/dsh-notifier