We drive personal Telegram over MTProto with Telethon — this acts as the user's own account (a "userbot"), so unlike the Bot API it can read full history, list every conversation, and act on anyone the user can reach.

Credentials are injected as env vars by the connector:

TELEGRAM_API_ID — app id
TELEGRAM_API_HASH — app hash — secret, never echo
TELEGRAM_SESSION_STRING — Telethon StringSession = full account access. Never log, echo, or print it. Treat it like the account password.

CLI

The skill ships scripts/tg.py — self-contained (the only third-party dep is telethon, preinstalled in the sandbox). Point a var at the shipped path and call it; no heredoc to re-create per turn, so a multi-step flow (dry-run → confirm) can't lose the helper between calls:

telegram

CLI