From cdcd53c2cd2eeb5e19d0dbe594abe8f823519cc7 Mon Sep 17 00:00:00 2001 From: teknium1 Date: Sat, 26 Sep 2026 11:21:57 -0700 Subject: [PATCH] chore(plugin-catalog): telegram-notify disclosure line, contributor map (catalog review) --- contributors/emails/madpower2000@gmail.com | 2 ++ plugin-catalog/telegram-notify.yaml | 6 +++++- 2 files changed, 7 insertions(+), 1 deletion(-) create mode 100644 contributors/emails/madpower2000@gmail.com diff --git a/contributors/emails/madpower2000@gmail.com b/contributors/emails/madpower2000@gmail.com new file mode 100644 index 0000000000..3afb1ff02d --- /dev/null +++ b/contributors/emails/madpower2000@gmail.com @@ -0,0 +1,2 @@ +madpower2000 +# PR #122816 catalog intake diff --git a/plugin-catalog/telegram-notify.yaml b/plugin-catalog/telegram-notify.yaml index 3a3b86088b..cf242a9408 100644 --- a/plugin-catalog/telegram-notify.yaml +++ b/plugin-catalog/telegram-notify.yaml @@ -5,7 +5,11 @@ description: >- Remote Telegram lifecycle notifications for the main Hermes agent: turn start, completion with a bounded final answer, interruption/failure, and user-facing approval requests. Suppresses subagent and automatic/smart-approval - noise. Outbound-only, no input channel. + noise. Outbound-only, no input channel. Disclosure — enabled by default once installed and + reuses the core Telegram gateway's TELEGRAM_BOT_TOKEN and TELEGRAM_HOME_CHANNEL when present, + so each main-agent turn's final answer (up to 3,200 chars) and approval-request command text + (up to 700 chars) from CLI, Desktop and any gateway platform are sent to api.telegram.org for + delivery to that one chat; token and state are stored 0600 under HERMES_HOME/telegram-notify. maintainer: madpower2000 tier: community category: automation