Summary

• The WhatsApp deliver callback in process-message.ts forwarded all payload kinds (tool, block, final) to WhatsApp
• block payloads contain the model's reasoning/thinking content, which should only be visible in the internal web UI
• This caused chain-of-thought to leak to end users as separate WhatsApp messages

The fix adds an early return for non-final payloads, matching how Telegram already filters by info.kind === "final".

Changes

• src/web/auto-reply/monitor/process-message.ts — skip delivery for info.kind !== "final"

Test plan

• Enable reasoning (thinkingDefault: "low") and send a message via WhatsApp — only the final response should appear
• Verify webchat/TUI still shows reasoning blocks as expected
• Verify Telegram behavior is unchanged

Fixes #24954
Fixes #24605

Made with Cursor

Greptile Summary

Fixes a bug where the WhatsApp deliver callback in process-message.ts forwarded all payload kinds (tool, block, final) to WhatsApp, causing chain-of-thought/reasoning content to leak to end users as separate messages. The fix adds an early return for info.kind !== "final", consistent with the repository's policy that only final replies should be delivered to external messaging surfaces. Dead code paths for tool and block payloads are correctly cleaned up.

• Added early return guard for non-final payloads in the WhatsApp deliver callback
• Removed now-unreachable tool-kind early return and block-kind conditional branches
• Simplified skipLog (hardcoded false) and shouldLog (no longer needs kind check) since only final payloads reach the delivery code
• Aligns WhatsApp behavior with the established AGENTS.md rule: "Never send streaming/partial replies to external messaging surfaces"

Confidence Score: 5/5

• This PR is safe to merge — it's a straightforward, well-scoped bug fix with correct dead code cleanup.
• The change is minimal and focused: a single early-return guard that prevents non-final payloads from being delivered to WhatsApp. The subsequent dead code removal is logically consistent with the guard. The pattern matches how other channels (Telegram) already handle this. No new logic is introduced, no edge cases are missed, and the change aligns with the repository's explicit policy in AGENTS.md.
• No files require special attention.

_{Last reviewed commit: d818f96}

Context used:

• Context from dashboard - CLAUDE.md (source)