omnius 1.0.43 → 1.0.44

package/README.md

@@ -3510,6 +3510,11 @@ Connect the agent to a Telegram bot. Telegram can run in auto, chat, or action m
 /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 tools                              # Show unified Telegram tool policy
+/telegram tools group <chat>                 # Show a chat-scoped policy override
+/telegram tools panel <chat> [policy_chat]  # Send inline admin toggle buttons
+/telegram delete-message <chat> <msg> [reason] # Delete one message
+/telegram delete-messages <chat> <msg,msg> [reason] # Delete multiple messages
 /telegram delete-reaction <chat> <msg> --user <id> # Delete a message reaction
 /telegram delete-reactions <chat> --user <id>      # Delete recent reactions
 ```
@@ -3548,6 +3553,8 @@ The Telegram bridge handles modern Bot API traffic directly:
 - **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.
+- **Unified Telegram tool** — Telegram-sourced agent runs receive one scoped `telegram` tool for Bot API operations. Read/media actions are available by default; janitorial deletion, reaction cleanup, moderation, bot-admin changes, and message send/edit actions require admin context plus explicit `telegramToolPolicy` enablement. Before group deletes or moderation, Omnius checks the bot's Telegram rights with `getMe` + `getChatMember` and returns the Bot API error if Telegram refuses the operation.
+- **Inline tool controls** — `/telegram tools panel <chat> [policy_chat]` sends an inline keyboard that toggles global or chat-scoped Telegram tool groups. Telegram callback queries are answered immediately so client spinners stop, and policy is persisted under `.omnius/settings.json`.
 - **TUI Telegram visibility** — Telegram quick-chat and action conversations register as blue plane-labeled views in the systems panel; clicking a view swaps the main scrollable window to that Telegram-only buffer, and the footer shows an active plane indicator while the bridge or Telegram work is active.
 
 ### Admin Slash Command Passthrough
@@ -3619,9 +3626,9 @@ Tools are gated per execution context. The system enforces strict separation bet
 | Context | Default Tools | Notes |
 |---------|--------------|-------|
 | `terminal` | All tools | Wide open — shell, file read/write, everything |
-| `telegram-admin-dm` | All except shell | Admin DM — full tools, shell blocked by default (overridable) |
-| `telegram-admin-group` | Read-only + web + vision/OCR + scoped reminders | Admin in public group — no system mutation tools |
-| `telegram-public` | Memory r/w, web fetch/search, scoped creative tools, scoped minimal reminders | Public users — no arbitrary local file access or shell |
+| `telegram-admin-dm` | All except shell + scoped `telegram` tool | Admin DM — full tools, shell blocked by default (overridable); Telegram janitorial/moderation actions still require explicit policy and Bot API rights |
+| `telegram-admin-group` | Read-only + web + vision/OCR + scoped reminders + scoped `telegram` tool | Admin in public group — current-chat only; high-risk Telegram actions require policy enablement |
+| `telegram-public` | Memory r/w, web fetch/search, scoped creative tools, scoped minimal reminders + read/media `telegram` actions | Public users — no arbitrary local file access, shell, moderation, bot-admin, or janitorial actions |
 | `api` | All tools | API endpoint — configurable |
 
 **System tools** (`shell`, `file_write`, `file_edit`, `file_read`, `file_patch`, `batch_edit`, `grep_search`, `glob_find`, `list_directory`, `code_sandbox`, `codebase_map`, `git_info`, etc.) are **never exposed** in public-facing contexts.