fix: populate currentThreadTs in threading tool context fallback for Telegram DM topics (#52217)

Lukavyi · obviyus · commit c3da19410603 · 2026-03-24T08:25:29.000+05:30
When a channel plugin lacks a custom buildToolContext (e.g. Telegram), the fallback path in buildThreadingToolContext did not set currentThreadTs from the inbound MessageThreadId. This caused resolveTelegramAutoThreadId to return undefined, so message tool sends without explicit threadId would route to the main chat instead of the originating DM topic. Fixes #52217
diff --git a/src/auto-reply/reply/agent-runner-utils.ts b/src/auto-reply/reply/agent-runner-utils.ts
@@ -48,10 +48,13 @@ export function buildThreadingToolContext(params: {
   // Fallback for unrecognized/plugin channels (e.g., BlueBubbles before plugin registry init)
   const threading = provider ? getChannelPlugin(provider)?.threading : undefined;
   if (!threading?.buildToolContext) {
+    const threadTs =
+      sessionCtx.MessageThreadId != null ? String(sessionCtx.MessageThreadId) : undefined;
     return {
       currentChannelId: originTo?.trim() || undefined,
       currentChannelProvider: provider ?? (rawProvider as ChannelId),
       currentMessageId,
+      currentThreadTs: threadTs || undefined,
       hasRepliedRef,
     };
   }
