Bug report: Two regressions after 2026.3.2 update
Issue 1: UI webchat replies bleeding into Telegram
Before the update, UI and Telegram were isolated — messages sent from the Control UI stayed in the UI only. After 2026.3.2, any conversation in the UI also sends replies to Telegram, even when Telegram hasn't been touched in that session.
Issue 2: Duplicate messages being sent
Replies are being sent twice — once as the inline assistant response, once via the message tool (or some internal double-send). This happens intermittently across both UI and Telegram sessions.
Both issues started immediately after updating to 2026.3.2. Suspect the streaming: "partial" change is affecting reply routing/deduplication logic.
Config: Single agent (main), Telegram dmPolicy: allowlist, streaming: partial
Before the update, UI and Telegram were isolated — messages sent from the Control UI stayed in the UI only. After 2026.3.2, any conversation in the UI also sends replies to Telegram, even when Telegram hasn't been touched in that session.
Issue 2: Duplicate messages being sent
Replies are being sent twice — once as the inline assistant response, once via the message tool (or some internal double-send). This happens intermittently across both UI and Telegram sessions.
Both issues started immediately after updating to 2026.3.2. Suspect the streaming: "partial" change is affecting reply routing/deduplication logic.
Config: Single agent (main), Telegram dmPolicy: allowlist, streaming: partial
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
