You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automatically rename Telegram DM forum topics when the first message arrives in a new topic/session. Currently users must either manually rename topics or instruct the agent to do it via SOUL.md/system prompt - which is unreliable since the model may ignore the instruction.
Problem
When using Telegram DM topics (forum mode in 1:1 bot chats), new topics get generic names like "Topic #123". Users have to:
Manually rename each topic, OR
Add instructions to SOUL.md/MEMORY.md telling the agent to rename - but this is model-dependent and unreliable (the agent frequently forgets)
This is a gateway-level concern, not something that should depend on model compliance.
Proposed Solution
Add an autoTopicLabel config option to TelegramDirectConfig and/or TelegramAccountConfig:
Summary
Automatically rename Telegram DM forum topics when the first message arrives in a new topic/session. Currently users must either manually rename topics or instruct the agent to do it via SOUL.md/system prompt - which is unreliable since the model may ignore the instruction.
Problem
When using Telegram DM topics (forum mode in 1:1 bot chats), new topics get generic names like "Topic #123". Users have to:
This is a gateway-level concern, not something that should depend on model compliance.
Proposed Solution
Add an
autoTopicLabelconfig option toTelegramDirectConfigand/orTelegramAccountConfig:{ "telegram": { "direct": { "63448508": { "autoTopicLabel": true } } } }Behavior
When
autoTopicLabel: trueand a message arrives in a DM topic:isFirstTurnInSessionalready exists inget-reply-run.ts)renameTopic()(API already exists and works)Implementation Notes
isFirstTurnInSessiondetection already exists insrc/auto-reply/reply/get-reply-run.ts:235renameTopicAPI is fully functional viaextensions/telegram/runtime-api.tseditForumTopicaction permission exists inTelegramActionConfigactions.editForumTopicpermissionAlternatives Considered
message:sent: Would work but adds complexity; a config flag is cleaner/set_topic_namecommand: PR feat: add /set_topic_name for telegram topic labels #46983 adds this, but does not solve the auto-rename caseRelated
/set_topic_namecommand (manual rename)