PR #78726: telegram: avoid silent fallback after message tool send (#78685)

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

Description (problem / solution / changelog)

Root cause

Telegram inbound dispatch tracks user-visible replies with deliveryState when the buffered reply pipeline calls deliverReplies / durable final delivery. The agent message tool sends via deliverOutboundPayloads, which succeeded but never updated that tracker. An empty/no visible final assistant payload then triggered the rewritten silent-reply fallback (“Nothing further to report.” etc.) even though Telegram already showed the tool-delivered reply.

Fixes https://github.com/openclaw/openclaw/issues/78685 .

Approach

Correlate the active inbound telegram turn (SessionKey → chat/account) with telegram outbound message:sent successes: when outbound delivery reports success for channel=telegram and the same to/account, call deliveryState.markDelivered() via the inbound snapshot.

Safety

Scoped to Telegram + matching session key/outbound recipient; clears when inbound dispatch ends. Uses existing outbound send success semantics (already used for diagnostics/hooks).

Runtime / security

No change to Telegram auth/pairing, gateway auth models, sandboxing, or tool ACLs — delivery correlation only affects whether the rewritten silent filler is skipped after proven outbound visibility.

Real behavior proof

Manual reproduction of the duplicate message in a live Telegram DM was not reliable (automatic DM policy steers trivial turns away from message-tool-only paths, so the buggy combination was hard to trigger on demand). Automated tests assert the correlation path (match → mark delivered, wrong to → no mark, end handler prevents double marks after cleanup).

Informal manual checks on a local gateway + Telegram bot (openclaw 2026.5.6) continued to show normal single-reply DM behavior after the change.

Tests run

pnpm test src/infra/outbound/telegram-inbound-turn-delivery.test.ts
node scripts/run-oxlint.mjs --tsconfig config/tsconfig/oxlint.core.json src/infra/outbound/telegram-inbound-turn-delivery.ts src/infra/outbound/deliver.ts
node scripts/run-oxlint.mjs --tsconfig config/tsconfig/oxlint.extensions.json extensions/telegram/src/bot-message-dispatch.ts
pnpm check:changed

Out of scope

• Broader refactoring of telegram delivery trackers.
• Matching other outbound channels unless the same symptom is confirmed there.

Changed files

• CHANGELOG.md (modified, +1/-0)
• extensions/telegram/src/action-runtime.test.ts (modified, +51/-0)
• extensions/telegram/src/action-runtime.ts (modified, +17/-0)
• extensions/telegram/src/bot-message-dispatch.ts (modified, +10/-0)
• extensions/telegram/src/channel-actions.test.ts (modified, +28/-0)
• extensions/telegram/src/channel-actions.ts (modified, +10/-2)
• src/infra/outbound/deliver.ts (modified, +8/-0)
• src/infra/outbound/telegram-inbound-turn-delivery.test.ts (added, +54/-0)
• src/infra/outbound/telegram-inbound-turn-delivery.ts (added, +45/-0)
• src/plugin-sdk/outbound-runtime.ts (modified, +5/-0)