Problem
When receiving messages from Telegram forum topics, the inbound metadata currently includes:
- (the numeric thread ID)
- But NOT the topic name/title
This makes it impossible for agents to automatically identify which topic file to load, since they only receive the numeric ID.
Current behavior
In a Telegram forum chat, agents receive:
But NOT the topic name (e.g., "Design-learning").
Expected behavior
Include the forum topic name/title so agents can:
1 in the metadata. Auto-match to topic files (e.g., )
2. Provide better contextual responses without manual mapping
Suggested solution
Add to the inbound metadata envelope for Telegram forum topic messages.
Example:
Context
This would enable agents to automatically load the correct topic memory file based on the topic name, without requiring manual ID-to-name mapping files.
Thanks!
Problem
When receiving messages from Telegram forum topics, the inbound metadata currently includes:
This makes it impossible for agents to automatically identify which topic file to load, since they only receive the numeric ID.
Current behavior
In a Telegram forum chat, agents receive:
But NOT the topic name (e.g., "Design-learning").
Expected behavior
Include the forum topic name/title so agents can:
1 in the metadata. Auto-match to topic files (e.g., )
2. Provide better contextual responses without manual mapping
Suggested solution
Add to the inbound metadata envelope for Telegram forum topic messages.
Example:
Context
This would enable agents to automatically load the correct topic memory file based on the topic name, without requiring manual ID-to-name mapping files.
Thanks!