syncended/deepseek-harness-messenger

Telegram bridge for DSH: drive sessions, models and approvals from chat, with allowlists, inline controls and optional voice transcription.

Puts a running DSH behind Telegram without a second frontend. A Messengers page in Settings stores the bot token through the DSH credential store and reconfiguration is live — no Host restart. From /start or /menu the buttons cover session listing and resuming persisted top-level sessions, workspace choice for new sessions, provider-grouped paginated model selection, reasoning level, permission preset, context pressure and cumulative token usage, and turn cancellation. Interactive ask_user_question prompts are answerable as buttons, multi-selects or free text; photos and image documents become image prompts with their captions intact. Long answers are split at Telegram's 4096-character limit without breaking formatting, and one slow chat does not block the others. The README is careful about where the plugin stops: the adapter owns protocol, polling and message primitives only, permission changes still go through DSH's permission-preset service rather than bypassing sandbox or approval policy, and it states outright that an enabled setting is not proof of connectivity — the Host logs are where token validation, TLS and webhook conflicts actually show up.

Messaging & Communication ★ 0
View on GitHub ↗

Install

dsh plugin --profile web add -w --config.auto-install-peers=false @syncended/dsh-messenger

The README's own line, and the flags are not decoration: -w is the workspace-root flag and the peer setting has to stay disabled for the pnpm-backed profile this was written against, so the line ships exactly as published rather than trimmed to a bare form. Settings can also be written by hand into the existing messenger row of ~/.dsh/profiles/web/cordis.patch.yml — the README warns not to add a duplicate row with the same id — and then the Host needs a restart, where Web-settings changes apply live.

Compatibility

Node.js 22 or newer, and DeepSeek Harness 0.1.2-rc.1 or a compatible Web profile providing storageDomain, fs and attachments. The adapter is disabled by default and cannot be enabled until at least one allowed chat ID is configured; group chats are off unless privateChatsOnly: false and explicit operator ids are listed. The credential reference is fixed to TELEGRAM_BOT_TOKEN so the plugin cannot resolve, overwrite or remove a credential belonging to another integration, and token values are syntax-checked before any request is sent. Local Whisper transcription is opt-in: the npm tarball carries the controller and python/worker.py, not Python, wheels or model weights, and the worker process exits once its queue drains, releasing RAM and VRAM.

Details

Alternatives

sliverp/DeepSeek-harness-weixin · sliverp/DeepSeek-harness-lark · sliverp/DeepSeek-harness-dingtalk

More plugins in Messaging & Communication

Browse more in Messaging & Communication

Guides for Messaging & Communication plugins