feat: Telegram long-polling mode as alternative to webhooks#7363
Open
flobo3 wants to merge 3 commits intoagno-agi:mainfrom
Open
feat: Telegram long-polling mode as alternative to webhooks#7363flobo3 wants to merge 3 commits intoagno-agi:mainfrom
flobo3 wants to merge 3 commits intoagno-agi:mainfrom
Conversation
Contributor
PR TriageMissing tests: This PR modifies source code but does not include any test changes. Please add or update tests to cover your changes. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Telegram interface currently only supports webhook mode, which requires a publicly accessible HTTPS URL, a FastAPI/uvicorn server, and TLS certificate management. This is overkill for local development, machines behind NAT, or simple single-process deployments.
Fixes #7362
Solution
Add
mode="polling"to theTelegramclass that runs without any web server:Architecture
Three new files, zero changes to existing code:
processor.pyTelegramMessageProcessor— mirrors the processing logic fromrouter.pyclosures into a reusable classpolling.pyTelegramPolling— long-poll loop usingbot.get_updates(offset, timeout)with backgroundasyncio.create_taskper messagetelegram.pymodeparam,start_polling()(async),run_polling()(sync)router.pyis completely untouched — full backward compatibility. All 117 existing tests pass without modification.Key design decisions
run_polling()is pure asyncio, no uvicorn neededtelebot.types.Message→ dict via.json()method, soprocess_message()receives the same format as webhook payloadsasyncio.create_task()so the poll loop is never blockedChecklist
modedefaults to"webhook")