PR #59714: fix(dedup): extend targetsMatchForSuppression to all channels, fix Slack duplicate delivery

• Repository: openclaw/openclaw
• Author: Aftabbs
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/59714

Description (problem / solution / changelog)

Summary

Fixes #59687 — Slack messages were being delivered twice when an agent both called the message tool and produced response text, because the dedup suppression logic (targetsMatchForSuppression) only performed semantic target normalization for Telegram.

Root cause

targetsMatchForSuppression() had a hard-coded if (provider !== "telegram") guard that short-circuited to a plain string equality check for all non-Telegram channels. For Slack, the message tool target (e.g. "C12345678") and the auto-delivery target (e.g. "channel:c12345678") are semantically equivalent but string-different after normalization, so the suppression check always returned false → duplicate delivery.

Fix

• Replaced the Telegram-only branch with a generic channel-aware approach: parseExplicitTargetForChannel(provider, ...) is tried for all channels via the plugin registry.
• Added built-in fallback parsers for Telegram and Slack that activate when the channel plugin is not registered, so Telegram topic-thread matching still works in environments without the full plugin registry (this also fixes 3 pre-existing failing tests on main).
• Thread-aware comparison logic (topic thread IDs) now applies uniformly to all channels.

Tests

• All 16 pre-existing tests pass (including 3 that were failing on main).
• Added 3 new Slack-specific suppression tests.

Test plan

• DM an agent bound to Slack; agent responds via message.send + produces response text → only one message appears in Slack
• Same test in a Slack channel thread → only one message in the thread
• Run pnpm vitest run src/auto-reply/reply/reply-payloads.test.ts → 19/19 pass

Changed files

• src/auto-reply/reply/reply-payloads-dedupe.ts (modified, +35/-10)
• src/auto-reply/reply/reply-payloads.test.ts (modified, +30/-0)
• src/cron/isolated-agent/delivery-dispatch.named-agent.test.ts (modified, +2/-0)

PR #60049: fix: provider-agnostic dedup + filter reasoning blocks from Slack streaming

• Repository: openclaw/openclaw
• Author: vision-ifc
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/60049

Description (problem / solution / changelog)

Fixes #59687

Summary

Two bugs in the Slack message delivery pipeline:

Bug 1 — targetsMatchForSuppression() skips non-Telegram channels

The function hard-coded 'telegram' as the provider when calling parseExplicitTargetForChannel, so thread-aware reply deduplication only worked for Telegram. When an agent called message.send to reply AND OpenClaw auto-delivered the response text on Slack (or any other channel), users received both messages.

Fix: Pass params.provider instead of 'telegram' so all channels get the same dedup logic.

Bug 2 — deliverWithStreaming() leaks reasoning/thinking blocks to Slack

When nativeStreaming: true was enabled for a Slack session, extended thinking blocks (isReasoning: true) from Claude were streamed to the Slack channel as visible messages.

Fix: Added an early return at the top of deliverWithStreaming() in the Slack dispatch: if (payload.isReasoning) return;

Changes

• extensions/slack/src/monitor/message-handler/dispatch.ts — reasoning block filter
• core/src/reply-payloads/dedupe.ts — provider-agnostic target comparison
• 4 new Slack dedup tests + existing 14 streaming tests still pass
• 4 files changed, 72 insertions, 6 deletions

Changed files

• extensions/slack/src/monitor/message-handler/dispatch.streaming.test.ts (modified, +15/-0)
• extensions/slack/src/monitor/message-handler/dispatch.ts (modified, +7/-0)
• src/auto-reply/reply/reply-payloads-dedupe.ts (modified, +9/-6)
• src/auto-reply/reply/reply-payloads.test.ts (modified, +41/-0)