Summary

Two related UX issues observed after a recent OpenClaw update, both on Telegram (direct chat).

Bug 1: Messages deleted after delivery

What happened:
When sending multiple messages in rapid sequence (text labels + voice notes), Telegram showed all messages arriving as expected — then they were deleted one by one immediately after, leaving only the voice note messages.

Steps to reproduce:

1. Send 4+ messages in quick succession (alternating text + media/voice)
2. Observe messages appearing in Telegram
3. Text-only messages then get deleted shortly after, media messages remain

Expected behavior: All sent messages remain visible.

Actual behavior: Text messages are retroactively deleted after delivery, presumably by OpenClaw's deduplication or multi-message suppression logic.

This is particularly disruptive — the user sees the messages arrive, reads them, then they disappear. If this is the "fix" for the multiple-messages issue, it's overcorrecting.

Bug 2: Persistent typing indicator

What happened:
The Telegram "Andy ••• typing" indicator appears non-stop during heavy sessions with many sequential tool calls (exec, file writes, message sends).

Expected behavior: Typing indicator clears promptly between tool calls or when the agent is idle.

Actual behavior: Indicator persists continuously, giving the impression the agent is stuck/looping.

Environment

• OpenClaw version: 2026.2.24 (df9a474)
• Channel: Telegram (direct chat)
• Runtime: agent=main, model=anthropic/claude-sonnet-4-6

Notes

Bug 1 may be related to a recent fix for duplicate/multiple message sending. The deletion behavior suggests the new logic is identifying previously-sent messages as duplicates and cleaning them up — but since they've already been delivered and seen, deletion is the wrong remediation.