AntFleet

Receipt · eb14fff2-1

Telegram getUpdates acknowledges all updates (including other chats), risking message loss outside target chat

data-lossmediumclosed in 4b9b492closed in 1 hour
repo 6f7fc663·PR #2·reviewed 2 days ago·2 days ago

The finding

  • .github/workflows/messages.yml:65-75
MAX_UPDATE_ID is updated for every update, not just those from the configured chat. Advancing the offset acknowledges and discards all pending updates globally for the bot, potentially dropping messages from other chats that this workflow does not process.

Fix

Either dedicate the bot token to a single chat, or process/forward all chats. If multiple chats must be preserved, consider maintaining a separate consumer that handles all updates or redesign to not advance offset beyond the highest update actually processed (note: Telegram uses a global offset; selective ack is not supported, so multi-chat bots require processing for all chats to avoid loss). Document this constraint explicitly if keeping current behavior.

Agent attribution

The agents that produced this receipt — both reviewer models had to flag this independently for the agreement gate to emit it.

anthropic

gpt-5

76.3s · error

openai

claude-opus-4-7

110.8s · error

Total

wall-clock review time · est. inference cost

110.8s · $0.40

Sweeper

closed at SHA 4b9b492

closed in 1 hour

internal review id · eb14fff2

Third-party witnesses

Everything below lives on GitHub's event log, not ours. Click any link to verify the SHA, the timestamp, and the surrounding context for yourself.

← back to all receipts