dsh-telegram-notify

Configuration reference

The Settings page writes the profile patch for the telegram-notify row. The same fields remain editable in ~/.dsh/profiles/web/cordis.patch.yml:

- id: telegram-notify
  config:
    chatId: "123456789"
    tokenRef: TELEGRAM_BOT_TOKEN
    notifyTurnComplete: true
    notifyTurnError: true
    notifyTurnAborted: false
    notifyQuestions: true
    notifyPlanReviews: true
    notifyApprovals: true
    silent: false

Field	Default	Meaning
chatId	"" (disabled)	Target chat id, or @channelusername.
tokenRef	TELEGRAM_BOT_TOKEN	Credential reference holding the bot token.
token	unset	Literal token for headless/one-off runs. The Settings page never writes this; prefer tokenRef.
apiBase	https://api.telegram.org	Bot API base URL; only change for a local Bot API server.
silent	false	Send without a notification sound.
notifyTurnComplete	true	Completed turns.
notifyTurnError	true	Failed, blocked, and max-token turns.
notifyTurnAborted	false	Cancelled turns.
notifyQuestions	true	Pending user questions.
notifyPlanReviews	true	Plans waiting for approval.
notifyApprovals	true	Pending tool approvals.

The Settings page is keyed to the loader row id telegram-notify; mounting the plugin under a different id makes the page report the namespace as unavailable. The editable page fields are schemastery volatile config, so saves apply to the running plugin without a restart. Messages are plain text (no parse mode), so model output cannot break formatting or inject markup; text is clipped to Telegram's 4096-character limit.

If you also run a two-way Telegram bridge such as dsh-im, sessions handled by that bridge produce their own replies, and this plugin will additionally send turn notifications for them. Disable the bridge or turn off the turn toggles if that is noisy.