luzhengyangtx/dsh-telegram-duty ↗★ 0
@luzhengyangtx/dsh-telegram-duty
Telegram duty gateway for DeepSeek Harness: long-poll Telegram into a dedicated duty session, global approval forwarding while on duty, and a local/duty watch toggle.
AI 分析
核心用途是通过 Telegram 远程接收和审批 DSH 任务。适合需要离线或移动端值班、远程管控 Agent 执行过程的用户。
インストール
$
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:luzhengyangtx/dsh-telegram-dutyドキュメント
README 全文を読む ↗Configuration
All fields live in the telegram-duty settings namespace (the web Settings page shows it, or put them under the patch row's config:).
| Field | Default | Meaning |
|---|---|---|
token | — | Bot token (marked secret; never shown in settings UIs). Alternatively set credentialsFile to a JSON file with token / chat_id / proxy. |
chatId | — | Whitelisted chat id. |
proxy | (empty) | HTTP proxy used for Bot API calls. Leave empty for a direct connection — only set a local proxy (e.g. http://127.0.0.1:7890) when Telegram is blocked in your network. |
sessionId | telegram-duty | Stable DSH session id; created on first message. |
dutyCwd | process cwd | Workspace directory of the duty session. |
approvalTimeoutMinutes | 10 | Unanswered approvals are rejected after this. |
watchMode | local | local (web popups) or duty (approvals to Telegram). |
language | en | Language of all Telegram messages: en or zh. |
dataDir | /storages/telegram-duty | Offset persistence directory. |
credentialsFile | — | Optional JSON file { token, chat_id, proxy } for credentials defaults. |
replyChunkChars | 3800 | Split threshold for long replies (Telegram limit 4096). |