Telegram channel plugin: bun server.ts processes consume ~80% CPU when idle

Description

Two bun server.ts child processes spawned by the claude-channel-telegram plugin consume extreme CPU when idle — ~101 hours of CPU time accumulated over just ~2.2 hours of wall time, with zero incoming Telegram messages.

Environment

• Ubuntu Linux 6.8.0, 2-core VPS, 4GB RAM
• Claude Code running as systemd service
• Plugin: claude-channel-telegram 0.0.1 (grammy ^1.21.0)
• Bun runtime
• DM policy: allowlist, no pending pairings, no activity

Observed behavior

• Two bun server.ts processes are spawned (two separate parent bun run wrappers)
• Each child process uses 35-45% CPU continuously, even with no messages
• SIGTERM does not stop them — requires SIGKILL
• After killing and letting Claude Code respawn them, new processes behave normally (<1% CPU)

Expected behavior

Idle Telegram plugin processes should consume near-zero CPU.

Possible cause

Likely a busy-loop or tight polling cycle in the long-polling/webhook handler that doesn't back off when there's no activity.