Telegram CLI

Use the local MTProto/Telethon script for the user's personal account; Telegram Bot API cannot read it.

Quick rules

• Prefer reads first, then propose the action queue.
• Write commands are dry-run by default and require --execute.
• Never run any write command with --execute unless the user explicitly approved that specific action or batch first.
• For send, present the draft first; send --execute requires approval of the final recipient and text.
• Mark-read/archive/mute are still Telegram writes; use them only after the user has approved the batch/action.
• Do not add edit/delete/bulk export/background automation unless the user explicitly asks.
• Treat the Telethon session like a high-privilege secret.
• Assume unread preservation is best-effort until tested on a real chat.

Setup

Use the skill-local launcher and cached virtualenv. Read local setup for bootstrap, authentication, config, or encrypted credentials, and setup and safety for auth/unread-state behavior. scripts/telegram-readonly remains a compatibility alias.