Files
openclaw/src
Clawdbot eef247b7a4 fix: auto-inject Telegram forum topic threadId in message tool
When using Telegram DM topics (forum topics), messages sent via the
message tool (media, buttons, etc.) land in General Topic instead of
the user's current topic. This happens because Slack has
resolveSlackAutoThreadId for auto-threading but Telegram had no
equivalent.

Add resolveTelegramAutoThreadId that mirrors the Slack pattern:
- When channel is telegram and no explicit threadId is provided
- Check if toolContext.currentThreadTs (the topic ID) is set
- Verify the target matches the originating chat
- Inject the threadId into params so the Telegram plugin action
  handler picks it up for sendMessage/sendMedia

The subagent announce path already correctly passes threadId via
requesterOrigin (set from agentThreadId in sessions-spawn-tool),
so no changes needed there.
2026-02-06 00:23:04 +05:30
..
2026-01-30 03:16:21 +01:00
2026-02-05 07:56:16 +00:00
2026-02-04 10:37:14 -05:00
2026-02-02 04:58:32 -08:00
2026-02-02 23:45:05 -08:00
2026-01-30 03:16:21 +01:00
2026-02-04 19:09:52 -05:00
2026-02-02 23:45:05 -08:00
2026-02-05 19:51:00 +09:00
2026-02-03 06:10:19 +00:00