emreturkmencom/antigravity-telegram-suite: source audit, 2026-10-10
Read from the source at commit 3688766dd95a; 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 your chat ID, but an allowed chat has unconfirmed shell on the host: /cmd runs text as a command, and the shipped .env turns on auto-accept, which clicks the agent's Run and Allow prompts for you. It also commits an encoded Google OAuth client secret in .env.example.
What the source shows
| Answer | Where | |
|---|---|---|
| Who can use it | Serves nobody until you list your Telegram ID | src/index.js:173 — if (!ALLOWED_CHAT_IDS.includes(ctx.chat.id.toString())) return |
| With no allowlist set | ALLOWED_CHAT_ID (empty = process exits) | src/index.js:141-150 — SECURITY ERROR: ALLOWED_CHAT_ID is required; process.exit(1) |
| Before the agent acts | runs the agent with permission prompts switched off | .env.example:51 — AUTOACCEPT_DEFAULT=true; src/index.js:1253-1261 — /cmd passes text to child_process.exec |
| Bot token | Read from the environment or a config file; no real token is committed | |