better-tg-cli 0.32.0 → 0.33.0
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.md +4 -3
- package/dist/telegram.mjs +1 -1
- package/package.json +1 -1
- package/skills/better-tg-cli/reference.md +3 -2
package/README.md
CHANGED
|
@@ -284,15 +284,16 @@ them to `telegram mcp --remote` on your computer, which keeps the session, the w
|
|
|
284
284
|
audit log. No tunnel, no token to paste.
|
|
285
285
|
|
|
286
286
|
```bash
|
|
287
|
-
telegram mcp --remote --read-only
|
|
288
|
-
telegram remote
|
|
287
|
+
telegram mcp --remote --read-only # keep it running (tmux, or a login item); drop --read-only to allow writes
|
|
288
|
+
telegram remote email you@example.com # once: link your email (a code is mailed to confirm it)
|
|
289
289
|
```
|
|
290
290
|
|
|
291
291
|
On macOS, start `--remote` in a terminal on the Mac itself (or a tmux session started there), not
|
|
292
292
|
over SSH: the confirmation dialog can't appear in an SSH session, so every app would be refused.
|
|
293
293
|
|
|
294
294
|
In the app, add a custom connector with the URL `https://mcp.better-tg-cli.com/mcp`. Its sign-in
|
|
295
|
-
page asks for
|
|
295
|
+
page asks for your email and mails you a code; enter it, then confirm in the dialog on your computer.
|
|
296
|
+
Without a linked email, `telegram remote pair` gives a one-time code for the same page. An agent can't
|
|
296
297
|
answer that dialog, so nothing connects without you. `telegram remote clients` lists connected apps,
|
|
297
298
|
`telegram remote revoke <id>` (or `--all`) disconnects them, and `telegram remote reset` also
|
|
298
299
|
replaces this computer's device key. When the computer is off, the app gets "your computer is
|