v2.0.1 — Chat permissions, visual media and controlled sending

Telegram Gateway now gives account owners explicit control over each chat, with photo/video-frame inspection and permission-controlled text sending.

New capabilities

• Per-chat permissions: independent read and send switches in /account. Every chat starts closed.
• Visual media: inspect_media returns a photo or a video frame at a requested timestamp. No audio transcription.
• Controlled sending: send_message requires the messages:send scope and chat permission. Durable request IDs prevent duplicate dispatch on retries.
• New account UI: Telegram-inspired layout, chat search, mobile support and dark mode.
• Release identity: /version, MCP initialization and container labels expose the running version and exact Git revision.
• Reproducible MinIO dependency: source build pinned to the original upstream commit, replacing the unavailable public registry image in CI and fresh-install instructions.

Upgrade requirements

1. Back up the database/configuration and check out v2.0.1.
2. Set TELEGRAM_AUTO_SYNC=false; automatic synchronization is no longer supported.
3. Build the updated image and apply migration 000016 using the installer. Native installations require FFmpeg.
4. Open /account, load chat names, and explicitly enable the desired read/send permissions. Existing tokens do not bypass the new policy.
5. Reconnect AI clients to consent to messages:send if needed. Message search now requires chat_id.

Version 2.0.1 is recommended over 2.0.0: it also fixes the unavailable MinIO registry dependency discovered during release verification.

Full changelog · Account management · Live version