better-tg-cli 0.31.1 → 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 +25 -0
- package/dist/telegram.mjs +1 -1
- package/package.json +2 -5
- package/skills/better-tg-cli/reference.md +6 -0
package/README.md
CHANGED
|
@@ -103,6 +103,7 @@ Every channel ships the same version from one release:
|
|
|
103
103
|
| Gemini CLI extension | skill and MCP server | `gemini extensions install https://github.com/TheVilfer/better-tg-cli` |
|
|
104
104
|
| Cursor, VS Code | MCP server | [one-click buttons](#mcp-server) |
|
|
105
105
|
| Grok Bot | MCP server over HTTP from your Mac | [see below](#grok-bot-remote-mcp-over-http) |
|
|
106
|
+
| claude.ai, ChatGPT and other apps that connect by URL | MCP through the hosted relay, session stays on your computer | [see below](#claudeai-chatgpt-and-other-apps-hosted-relay) |
|
|
106
107
|
| The CLI itself | agent skill for Claude Code, Codex, Cursor, Gemini CLI and 7 more | `telegram skill install` |
|
|
107
108
|
| [skills.sh](https://skills.sh) | agent skill for any shell agent | `npx skills add TheVilfer/better-tg-cli` |
|
|
108
109
|
| [MCP Registry](https://registry.modelcontextprotocol.io/v0/servers?search=better-tg-cli) | MCP server entry `io.github.TheVilfer/better-tg-cli` | through your MCP client |
|
|
@@ -275,6 +276,30 @@ tunnel URL plus `/mcp` (for example `https://<machine>.<tailnet>.ts.net/mcp`) an
|
|
|
275
276
|
for your tailnet first. A `cloudflared` quick tunnel gets a new URL on every start. Read "Remote
|
|
276
277
|
MCP over HTTP" in [SECURITY.md](SECURITY.md) first.
|
|
277
278
|
|
|
279
|
+
### claude.ai, ChatGPT and other apps (hosted relay)
|
|
280
|
+
|
|
281
|
+
claude.ai (web and mobile), ChatGPT and other apps that add MCP servers by URL sign in with OAuth
|
|
282
|
+
and can't start a local program. The hosted relay at `https://mcp.better-tg-cli.com/mcp` connects
|
|
283
|
+
them to `telegram mcp --remote` on your computer, which keeps the session, the write guard and the
|
|
284
|
+
audit log. No tunnel, no token to paste.
|
|
285
|
+
|
|
286
|
+
```bash
|
|
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
|
+
```
|
|
290
|
+
|
|
291
|
+
On macOS, start `--remote` in a terminal on the Mac itself (or a tmux session started there), not
|
|
292
|
+
over SSH: the confirmation dialog can't appear in an SSH session, so every app would be refused.
|
|
293
|
+
|
|
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 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
|
|
297
|
+
answer that dialog, so nothing connects without you. `telegram remote clients` lists connected apps,
|
|
298
|
+
`telegram remote revoke <id>` (or `--all`) disconnects them, and `telegram remote reset` also
|
|
299
|
+
replaces this computer's device key. When the computer is off, the app gets "your computer is
|
|
300
|
+
offline". The relay passes requests through without storing them, but it does see them: read
|
|
301
|
+
"Hosted relay" in [SECURITY.md](SECURITY.md). Its code is in [`relay/`](relay/).
|
|
302
|
+
|
|
278
303
|
## FAQ
|
|
279
304
|
|
|
280
305
|
**Will Telegram ban my account?**
|