Conversation
Add message_thread_id support to send_telegram_message so protocols
can be routed to topics within a single forum-style group instead of
separate chats. Configured via TELEGRAM_CHAT_ID_TOPICS and
TELEGRAM_TOPIC_ID_{PROTOCOL} env vars. Backwards compatible — protocols
without a topic ID keep using legacy per-protocol chat routing.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
message_thread_idsupport tosend_telegram_message()for routing protocols to topics within a single forum-style Telegram groupTELEGRAM_CHAT_ID_TOPICSandTELEGRAM_TOPIC_ID_{PROTOCOL}env vars; topics always use the default botLOG_LEVEL, wrong mock target)Closes #162
Test plan
TELEGRAM_CHAT_ID_TOPICSandTELEGRAM_TOPIC_ID_*env vars🤖 Generated with Claude Code