← Open-source Telegram bots

PleasePrompto/ductor: source audit, 2026-10-10

Read from the source at commit 3e3c88af57bc; the bot was not run (it needs a BotFather token). Each answer cites the file and line that shows it. All 20 bots

In short

Will not start without an allowlist. Once you are on it, the agent runs with all permission prompts bypassed on the host; the Docker sandbox exists but is off by default in code (the example config shows it on).

What the source shows

AnswerWhere
Who can use itServes nobody until you list your Telegram IDductor_bot/messenger/telegram/middleware.py:153 — elif user.id not in self._allowed_users: return None
With no allowlist setallowed_user_ids in ~/.ductor/config/config.json, default []; startup exits when emptyductor_bot/__main__.py:265-269 — needs_users = not config.allowed_user_ids ... sys.exit(1)
Before the agent actsruns the agent with permission prompts switched offductor_bot/config.py:439 — permission_mode: str = "bypassPermissions"; config.py:43 — Docker sandbox enabled: bool = False
Bot tokenRead from the environment or a config file; no real token is committed