better-tg-cli 0.37.0 → 0.38.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.es.md +3 -0
- package/README.md +36 -3
- package/README.ru.md +3 -0
- package/dist/telegram.mjs +1 -1
- package/package.json +5 -2
- package/skills/better-tg-cli/SKILL.md +64 -0
- package/skills/better-tg-cli/reference.md +233 -1
package/README.es.md
CHANGED
|
@@ -318,6 +318,9 @@ Linux. Por favor, informa de los problemas en los issues.
|
|
|
318
318
|
**¿Puedo usarlo desde Grok Bot, ChatGPT u otro agente en la nube?**
|
|
319
319
|
Los agentes en la nube no pueden iniciar un programa en tu ordenador, así que ejecuta el servidor MCP por HTTP y accede a él a través de un túnel. Consulta [Grok Bot](#grok-bot-mcp-remoto-por-http).
|
|
320
320
|
|
|
321
|
+
**El inicio de sesión falla con «NetSocket was closed» en un ordenador en la nube (Grok Bot y otros).**
|
|
322
|
+
Algunos ordenadores de agentes en la nube solo dejan salir HTTPS, y eso corta el transporte TCP de Telegram. La CLI cambia entonces sola a MTProto sobre WebSocket (`wss://*.web.telegram.org`, el transporte de web.telegram.org) y lo recuerda para el perfil. `TG_TRANSPORT=tcp|wss|auto` elige el transporte a mano.
|
|
323
|
+
|
|
321
324
|
**¿Cómo actualizo?**
|
|
322
325
|
Ejecuta `telegram update`. Usa el mismo canal desde el que instalaste: Homebrew, npm o un binario de release.
|
|
323
326
|
Si instalaste la skill de agente con `telegram skill install`, vuelve a ejecutarlo para actualizarla.
|
package/README.md
CHANGED
|
@@ -204,16 +204,46 @@ telegram get "Chat" 812 813 # exact messages by ID
|
|
|
204
204
|
telegram download "Chat" 812 # save the attached file
|
|
205
205
|
telegram sync --chat "Chat" --output ./export --resume # incremental markdown export
|
|
206
206
|
|
|
207
|
+
telegram drafts # saved but unsent drafts
|
|
208
|
+
telegram admin-log "Team" # a group's recent admin actions
|
|
209
|
+
telegram profile-photos @alice # a user's profile photos
|
|
210
|
+
telegram read @channel -n 20 --full # every message stat (views, reactions, flags, media)
|
|
211
|
+
telegram stats "Mock News" --graphs # full channel stats + growth graphs; --message <id> / --story <id> too
|
|
212
|
+
telegram sessions ; telegram stars # active login sessions; Telegram Stars balance & transactions
|
|
213
|
+
telegram invites "Team" --requests # a chat's invite links, or its pending join requests
|
|
214
|
+
|
|
207
215
|
telegram write-access on --for 1h # a human confirms this
|
|
208
216
|
telegram send @alice "on my way"
|
|
209
217
|
printf '%s' "$text" | telegram send @alice - # long or multi-line text: from stdin, no quoting problems
|
|
210
218
|
telegram reply "Chat" 812 "on it" --silent
|
|
211
219
|
telegram click @SomeBot 4410 "Settings" # press an inline button
|
|
220
|
+
telegram pin-chat @alice # pin a chat; mark-unread / delete-dialog too
|
|
221
|
+
telegram edit-permissions "Team" @alice --mute --until 1d # restrict a member; --lift to undo
|
|
222
|
+
telegram topic create "Dev Forum" "Release 2.0" # forum topics: create/edit/close/reopen/pin
|
|
223
|
+
|
|
224
|
+
telegram api messages.GetAllDrafts # call any raw TL method (full API reachability)
|
|
225
|
+
telegram api channels.GetAdminLog --params '{"channel":{"_chat":"Team"},"limit":20,"q":""}'
|
|
226
|
+
telegram messages get-history --peer @durov --limit 10 # or a typed command per TL method
|
|
227
|
+
telegram account get-authorizations # telegram <namespace> --help lists a namespace
|
|
228
|
+
telegram help get-config # telegram ping, telegram req-pq, … for root methods
|
|
212
229
|
```
|
|
213
230
|
|
|
214
|
-
Read commands take `--json`, and some also take `--markdown`.
|
|
215
|
-
`
|
|
216
|
-
|
|
231
|
+
Read commands take `--json`, and some also take `--markdown`. `read`/`get`/`search`/`inbox`/`watch`
|
|
232
|
+
take `--full` (alias `--stats`) to include every per-message statistic (views, forwards, full
|
|
233
|
+
reaction breakdown, comments, flags, rich media metadata) — default output is unchanged without it.
|
|
234
|
+
See all commands with `telegram help-all`. [reference.md](skills/better-tg-cli/reference.md) covers the behaviour that the flag list can't
|
|
235
|
+
explain: output shapes, threads, bot buttons, admin commands and troubleshooting. The generic
|
|
236
|
+
`telegram api <namespace.Method>` reaches 100% of the Telegram client API, and every one of the 823
|
|
237
|
+
TL methods also has its own typed top-level command `telegram <namespace> <method>` (root methods
|
|
238
|
+
like `telegram ping` too), generated from the schema with the same refusals and read/write guard as
|
|
239
|
+
`api`. Where a namespace name collides with a curated command (`stats`, `stories`, `contacts`,
|
|
240
|
+
`auth`, `folders`, `help`), the curated command is unchanged and the generated methods attach as
|
|
241
|
+
subcommands, picked only when the first word is exactly a method name (quote or use an ID for a
|
|
242
|
+
chat literally named like a method). Each method carries its official description and per-parameter
|
|
243
|
+
docs (from core.telegram.org): `telegram <namespace> --help` lists a namespace's methods marked
|
|
244
|
+
`[read]`/`[write]`/`[refused]`, `telegram <namespace> <method> --help` shows params, an example and
|
|
245
|
+
the docs link, and `telegram schema [<ns> [<method>]]` prints the same as JSON.
|
|
246
|
+
[docs/api-coverage.md](docs/api-coverage.md) tracks coverage against the schema and Telethon.
|
|
217
247
|
|
|
218
248
|
## MCP server
|
|
219
249
|
|
|
@@ -307,6 +337,9 @@ report problems in the issues.
|
|
|
307
337
|
**Can I use it from Grok Bot, ChatGPT or another cloud agent?**
|
|
308
338
|
Cloud agents can't start a program on your computer, so run the MCP server over HTTP and reach it through a tunnel. See [Grok Bot](#grok-bot-remote-mcp-over-http).
|
|
309
339
|
|
|
340
|
+
**Login fails with "NetSocket was closed" on a cloud computer (Grok Bot and others).**
|
|
341
|
+
Some hosted agent computers let only HTTPS out, which drops Telegram's TCP transport. The CLI then switches to MTProto over WebSocket (`wss://*.web.telegram.org`, the transport of web.telegram.org) by itself and remembers it for the profile. `TG_TRANSPORT=tcp|wss|auto` picks the transport by hand.
|
|
342
|
+
|
|
310
343
|
**How do I update?**
|
|
311
344
|
Run `telegram update`. It uses the same channel you installed from: Homebrew, npm or a release binary.
|
|
312
345
|
If you installed the agent skill with `telegram skill install`, run that again to refresh it.
|
package/README.ru.md
CHANGED
|
@@ -307,6 +307,9 @@ tailscale funnel --bg 8787 # или: cloudflared tunnel --url h
|
|
|
307
307
|
**Можно ли пользоваться из Grok Bot, ChatGPT или другого облачного агента?**
|
|
308
308
|
Облачный агент не может запустить программу на вашем компьютере, поэтому поднимите MCP-сервер по HTTP и откройте к нему туннель. См. [Grok Bot](#grok-bot-удалённый-mcp-по-http).
|
|
309
309
|
|
|
310
|
+
**Вход падает с «NetSocket was closed» на облачном компьютере (Grok Bot и другие).**
|
|
311
|
+
Некоторые облачные компьютеры агентов выпускают наружу только HTTPS, и TCP-транспорт Telegram обрывается. Тогда CLI сам переключается на MTProto поверх WebSocket (`wss://*.web.telegram.org`, тот же транспорт, что у web.telegram.org) и запоминает это для профиля. Выбрать транспорт вручную можно через `TG_TRANSPORT=tcp|wss|auto`.
|
|
312
|
+
|
|
310
313
|
**Как обновиться?**
|
|
311
314
|
`telegram update`. Команда обновляет тем же способом, каким CLI был установлен: Homebrew, npm или бинарник из релиза.
|
|
312
315
|
Если скилл для агентов ставили через `telegram skill install`, запустите её ещё раз, чтобы обновить скилл.
|