Problem

When reasoningLevel is "on" (either explicitly via /reasoning on or auto-enabled), reasoning/thinking content was being sent as a visible message to WhatsApp and other non-Telegram channels.

Two paths caused the leak:

1. Block reply path: handleMessageEnd emits reasoning via onBlockReply when includeReasoning is true
2. Final payload path: buildEmbeddedRunPayloads adds reasoning text to replyItems when reasoningLevel === "on"

Telegram has its own dispatch path (bot-message-dispatch.ts) that splits reasoning into a dedicated lane and handles suppression via splitTelegramReasoningText. The generic dispatch-from-config.ts path used by WhatsApp, web, and other channels had no such filtering.

Fix

• Add isReasoning?: boolean flag to ReplyPayload
• Tag reasoning payloads at both emission points (handlers.messages.ts and payloads.ts)
• Filter isReasoning payloads in dispatch-from-config.ts for both block reply and final reply paths

Telegram is unaffected: it uses its own deliver callback that detects reasoning via the Reasoning:\n prefix and routes to a separate lane.

Tests

• 2 new tests in dispatch-from-config.test.ts covering both suppression paths
• All existing tests pass (739 auto-reply tests, 46 Telegram dispatch tests)

Fixes #24954

Greptile Summary

Fixed reasoning/thinking content leak to WhatsApp, web, and other non-Telegram channels by adding an isReasoning flag to ReplyPayload and filtering these payloads in the generic dispatch path (dispatch-from-config.ts).

The fix addresses two leak paths:

• Block reply emissions from handleMessageEnd when includeReasoning is true
• Final payload emissions from buildEmbeddedRunPayloads when reasoningLevel === "on"

Telegram is unaffected since it uses a dedicated dispatch path (bot-message-dispatch.ts) with splitTelegramReasoningText that routes reasoning to a separate lane. This change only affects the generic dispatch path used by WhatsApp, web, and extension channels (msteams, feishu, matrix, mattermost, bluebubbles).

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix is surgical and well-tested, with clear filtering logic at both emission points. The isReasoning flag is properly tagged where reasoning payloads are created, and both the block reply and final reply paths in the generic dispatcher correctly filter these payloads. Telegram's existing reasoning handling is preserved through its separate dispatch path. The two new tests cover both suppression scenarios comprehensively.
• No files require special attention

_{Last reviewed commit: a65e7a9}