fix: prevent double Telegram polling loop on startup

[bluzername]

Problem

The Telegram bot daemon opens two concurrent connections to api.telegram.org on startup, which causes getUpdates to return 409 Conflict on every poll. Messages still work through retries but the logs are spammed with error messages nonstop.

I had this happening on one of my agents and the logs were full of 409 errors which made it hard to see the real activity.

Root Cause

startPolling() in src/commands/telegram.ts has no guard against being called twice. If initTelegram() is invoked twice before the first poll() enters its while (running) loop, two polling loops start concurrently - each opening its own TCP connection to Telegram API.

Fix

Added an isPolling flag that prevents startPolling() from running more than once:

let isPolling = false;

export function startPolling(debug = false): void {
  if (isPolling) return;  // already running, skip
  isPolling = true;
  // ...
}

The flag is also reset to false in the catch handler so if the first attempt fails completely, a retry can still work.

This is the exact fix suggested in the issue. Simple, no side effects, covers the race condition.

Closes #47

[moazbuilds]

@claude

[claude]

Claude Code is working…

I'll analyze this and get back to you.

View job run