open-agents-ai 0.187.581 → 0.187.583

package/README.md

@@ -3424,10 +3424,46 @@ Connect the agent to a Telegram bot. Each incoming message spawns a dedicated su
 /telegram                   # Toggle bridge on/off (uses saved key)
 /telegram status            # Show connection status + active sub-agents
 /telegram stop              # Disconnect and kill all sub-agents
+/telegram auth              # Show a one-time TUI-only admin auth code
+/telegram auth cancel       # Cancel the pending admin auth code
+/telegram bot <username> <text>              # Send bot-to-bot message by @username
+/telegram poll <chat> <question> | <a> [| <b>] # Send a poll
+/telegram live-photo <chat> <live> <photo> [caption] # Send a live photo
+/telegram draft <chat_id> <draft_id> [text]  # Set or clear a message draft
+/telegram admins <chat> [--bots]             # List chat administrators
+/telegram personal <user_id> <limit>         # Fetch profile personal chat messages
+/telegram access get <managed_bot_user_id>   # Show managed-bot access restrictions
+/telegram access set <managed_bot_user_id> <restricted|open> [user_ids] # Configure access
+/telegram delete-reaction <chat> <msg> --user <id> # Delete a message reaction
+/telegram delete-reactions <chat> --user <id>      # Delete recent reactions
 ```
 
 The bot token and admin ID are persisted to project settings, so you only need to set them once. After that, bare `/telegram` toggles the bridge on and off like a service watchdog.
 
+### Telegram Admin Authentication
+
+Run `/telegram auth` in the TUI to generate a one-time six-digit code. The code is rendered only in the terminal and is not inserted into agent prompts or Telegram sub-agent context. From the Telegram account that should become admin, send:
+
+```text
+/auth <code>
+```
+
+On success, that Telegram user ID is saved as the admin user and future private-DM slash commands are passed through the same command handler as the local TUI. `/telegram auth cancel` invalidates a pending code.
+
+### Bot API 10.0 Features
+
+The Telegram bridge handles modern Bot API traffic directly:
+
+- **Guest Mode** — inbound `guest_message` updates are normalized into regular agent work and answered through `answerGuestQuery`, so users can interact from profile-surface guest chats before a normal bot DM exists.
+- **Command menu registration** — when the bridge starts, OA registers the local slash-command surface with Telegram via `setMyCommands`; Telegram-safe names such as `/full_send_bless` are mapped back to canonical TUI commands like `/full-send-bless` before execution.
+- **Bot-to-bot sends** — `/telegram bot <username> <text>` targets another bot by username using Telegram's supported bot-to-bot message subset.
+- **Managed bot access** — `/telegram access get|set` reads and configures managed-bot access restrictions by managed bot user ID.
+- **Polls and live photos** — incoming polls, poll media summaries, option media, country/member limits, and live photos are captured as first-class Telegram message context; `/telegram poll` and `/telegram live-photo` send the matching Bot API payloads.
+- **Direct-message channels** — direct-message channel/topic metadata is preserved on normalized Telegram messages for routing and future adapter logic.
+- **Drafts and profile chat reads** — `/telegram draft` can set or clear message drafts, and `/telegram personal <user_id> <limit>` fetches recent messages from a user's profile personal chat.
+- **Reactions/admin helpers** — `/telegram delete-reaction` removes a message reaction, `/telegram delete-reactions` removes recent reactions by a user/chat, and `/telegram admins <chat> [--bots]` can include bot administrators.
+- **TUI sub-agent visibility** — Telegram conversations register as blue plane-labeled sub-agent views in the systems panel and show an active plane indicator in the footer while the bridge or Telegram sub-agents are active.
+
 ### Admin Slash Command Passthrough
 
 When the admin sends a `/command` in a private DM, it's routed directly through the terminal's command handler — the same code path as typing the command in the TUI. This means you can control the agent from your phone: