Bug type
Behavior bug (incorrect output/state without crash)
Summary
Hi team, I’m seeing duplicate outgoing replies on Telegram.
Environment:
- OpenClaw version: 2026.3.2
- Channel: Telegram (direct chat)
Issue:
- Each user message produces 2 assistant replies with identical content.
- One duplicate disappears later (looks like client-side/server dedup), but both are initially delivered.
What I already checked:
- Only one active agent session
- Telegram webhook reset (
deleteWebhook?drop_pending_updates=true)
- Bot token regenerated and updated in config
- No duplicate OpenClaw processes (no docker/tmux/screen/background duplicates)
- Still reproducible after updating to 2026.3.2
If useful, I can provide logs and exact startup command.
Steps to reproduce
It happens for all message exchanges with the bot on telegram.
Expected behavior
- One user message -> one assistant reply
Actual behavior
- One user message -> two identical assistant replies
OpenClaw version
2026.3.2
Operating system
Xubuntu 24.04
Install method
npm install -g openclaw@latest /// launched: openclaw gateway
Logs, screenshots, and evidence
Impact and severity
Affected: Telegram users
Severity: annoying
Frequency: always
Consequence: confusion with long replies
Additional information
Never tried openclaw before
Bug type
Behavior bug (incorrect output/state without crash)
Summary
Hi team, I’m seeing duplicate outgoing replies on Telegram.
Environment:
Issue:
What I already checked:
deleteWebhook?drop_pending_updates=true)If useful, I can provide logs and exact startup command.
Steps to reproduce
It happens for all message exchanges with the bot on telegram.
Expected behavior
Actual behavior
OpenClaw version
2026.3.2
Operating system
Xubuntu 24.04
Install method
npm install -g openclaw@latest /// launched: openclaw gateway
Logs, screenshots, and evidence
Impact and severity
Affected: Telegram users
Severity: annoying
Frequency: always
Consequence: confusion with long replies
Additional information
Never tried openclaw before