better-tg-cli 0.33.0 → 0.35.0-rc.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "better-tg-cli",
-  "version": "0.33.0",
+  "version": "0.35.0-rc.1",
   "description": "Telegram for your terminal and your AI agents: read, search, send and press bot buttons on your own account. MCP server included.",
   "mcpName": "io.github.TheVilfer/better-tg-cli",
   "keywords": [

package/skills/better-tg-cli/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: better-tg-cli
-description: Telegram on the user's own account through the `telegram` CLI (better-tg-cli). Read, search and send messages; read comments, threads and forum topics; press bot buttons; react, forward, pin, poll; manage chats, contacts and profile; watch live and export history. Use it when the user asks about Telegram messages, inbox or unread, wants to find something in chats, send or edit a message, talk to a bot, or manage a group or channel. Also «телеграм», «тг», «телега», «проверь телеграм», «что в тг», «напиши в телеграм», «прочитай чат», «найди в телеге».
+description: Telegram on the user's own account through the `telegram` CLI (Better-TG-CLI). Read, search and send messages; read comments, threads and forum topics; press bot buttons; react, forward, pin, poll; manage chats, contacts and profile; watch live and export history. Use it when the user asks about Telegram messages, inbox or unread, wants to find something in chats, send or edit a message, talk to a bot, or manage a group or channel. Also «телеграм», «тг», «телега», «проверь телеграм», «что в тг», «напиши в телеграм», «прочитай чат», «найди в телеге».
 ---
 
-# better-tg-cli
+# Better-TG-CLI
 
 `telegram <command>` runs on the user's own Telegram account (MTProto, not a bot). It works the same in any agent that has a shell. If the `telegram_read`, `telegram_write` and `telegram_help` MCP tools are available (`telegram mcp`), use them instead: they take the same argv as the CLI.
 

package/skills/better-tg-cli/reference.md

@@ -127,12 +127,6 @@ Buttons that need 2FA take `--password`. `--no-wait` skips waiting for the bot's
   `POST /mcp` (stateless, JSON responses) for remote hosts such as Grok Bot. Every request needs
   `Authorization: Bearer <token>` (`telegram mcp --token`, `--rotate-token`). Requests with an
   `Origin` header are refused. `--read-only` drops `telegram_write` (also works over stdio).
-- **Relay:** `telegram mcp --remote` connects this computer to the hosted relay
-  (`https://mcp.better-tg-cli.com/mcp`) for claude.ai, ChatGPT and other apps that connect by URL.
-  The user links an email once (`telegram remote email`) or pairs with `telegram remote pair`, and
-  confirms each app in a dialog; never do any of these for them. `telegram remote clients|revoke|reset`
-  manage connected apps. `remote` is not
-  available over MCP.
 
 ## Chat identifiers