telegram-notify.yaml 1.5 KB

1234567891011121314151617181920212223242526272829303132
  1. name: telegram-notify
  2. repo: https://github.com/madpower2000/hermes-telegram-notify
  3. sha: d7cab7dfb154425118129b0086032e873a832576
  4. description: >-
  5. Remote Telegram lifecycle notifications for the main Hermes agent: turn
  6. start, completion with a bounded final answer, interruption/failure, and
  7. user-facing approval requests. Suppresses subagent, Telegram-origin lifecycle,
  8. and automatic/smart-approval noise. Outbound-only, no input channel. Disclosure — enabled by default once installed and
  9. reuses the core Telegram gateway's TELEGRAM_BOT_TOKEN and TELEGRAM_HOME_CHANNEL when present,
  10. so each main-agent turn's final answer (up to 3,200 chars) and approval-request command text
  11. (up to 700 chars) from CLI, Desktop and eligible gateway platforms are sent to api.telegram.org for
  12. delivery to that one chat; Telegram-origin lifecycle and approval-prompt copies (and, when
  13. notify_on_approval_response is enabled, Telegram-origin approval-response copies) are suppressed
  14. because the core Telegram gateway already delivers them in that chat; token and state are
  15. stored 0600 under HERMES_HOME/telegram-notify.
  16. maintainer: madpower2000
  17. tier: community
  18. category: automation
  19. requires_hermes: ">=0.21.5"
  20. docs_url: https://github.com/madpower2000/hermes-telegram-notify
  21. version: "1.1.3"
  22. platforms: []
  23. capabilities:
  24. provides_tools: []
  25. provides_hooks:
  26. - pre_llm_call
  27. - post_llm_call
  28. - on_session_end
  29. - pre_approval_request
  30. - post_approval_response
  31. provides_middleware: []
  32. requires_env: []