better-tg-cli 0.36.0 → 0.37.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "better-tg-cli",
-  "version": "0.36.0",
+  "version": "0.37.0",
   "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

@@ -14,7 +14,7 @@ telegram help-all -g read >/dev/null && telegram check
 ```
 
 - **`telegram` is missing, or it has no `help-all`.** A different program is installed under that name. Ask the user before installing anything, then run `brew install thevilfer/tap/better-tg-cli` (macOS or Linux), `scoop install better-tg-cli` after `scoop bucket add thevilfer https://github.com/TheVilfer/scoop-bucket` (Windows), or `npm install -g better-tg-cli` (Node 20 or newer, any OS). Never install `@skillhq/telegram`: it is an old build, and bot replies come back as `(no text)`.
-- **"Not configured" or "Not authenticated".** Run `telegram onboard --json` (in the background if your tool times out before ~15 minutes). It opens a page on 127.0.0.1 where the user gets an invite or enters their own API keys, scans a QR code and types their 2FA password. You never see any of that. Tell the user the page is open (relay the `url` event if the browser didn't open), wait for the `done` event, then confirm with `telegram whoami`. Never run `telegram auth` yourself. Never ask for a login code, 2FA password, invite token or api_hash in chat, and never fill in the onboarding page yourself. If the user is on SSH or `onboard` can't open a page, ask them to run `telegram auth --qr` in their own terminal.
+- **"Not configured" or "Not authenticated".** Run `telegram onboard --json` (in the background if your tool times out before ~15 minutes). It opens a page on 127.0.0.1 where the user gets a login key or enters their own API keys, scans a QR code and types their 2FA password. You never see any of that. Tell the user the page is open (relay the `url` event if the browser didn't open), wait for the `done` event, then confirm with `telegram whoami`. Never run `telegram auth` yourself. Never ask for a login code, 2FA password, login key or api_hash in chat, and never fill in the onboarding page yourself. If the user is on SSH or `onboard` can't open a page, ask them to run `telegram auth --qr` in their own terminal.
 
 Before you use an unfamiliar flag, run `telegram help-all -g <word>`. It is generated from the code, so it is always current. For behaviour details (threads, bot buttons, sync, JSON shapes, errors), read `reference.md` next to this file.
 

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

@@ -142,13 +142,13 @@ matches titles.
 ## Troubleshooting
 
 - `Not configured`: run `telegram onboard --json`. It serves a one-shot page on 127.0.0.1 (random
-  secret path, closes when done, `--timeout` 15 min by default) where the user gets an invite from
+  secret path, closes when done, `--timeout` 15 min by default) where the user gets a login key from
   better-tg-cli.com (it comes back to the page by itself), or enters their own keys, then scans a QR
   code and types their 2FA password. Events: `url`, `waiting_invite`, `waiting_scan`, `need_password`,
   `done` (exit 0), `error`, `timeout` (exit 1); `already_logged_in` exits 0 without changes.
   `--no-open` only prints the URL. You never get tokens, codes or passwords, and you must not ask
   for them or fill in the page. Without a browser on this machine (SSH), the user runs
-  `telegram auth --qr` (own keys) or `telegram auth --invite --qr` in their terminal; that is
+  `telegram auth --qr` (own keys) or `telegram auth --login-key --qr` in their terminal; that is
   interactive, so never run it for them. `--qr` logs in by scanning a QR code in the Telegram app instead of
   typing a code (`TG_QR_INVERT=1` for light terminals).