opencode-telegram-connect 1.0.2 → 1.0.3

package/README.md

@@ -2,7 +2,7 @@
 
 Control a running OpenCode session from Telegram with your own bot. Messages are forwarded to OpenCode; answers, permission requests, and questions from the agent appear in Telegram. The plugin supports OpenCode on Windows, WSL, Linux, and macOS.
 
-**Telegram stays off when OpenCode starts.** The connection only begins when you ask your agent to connect and it calls `telegram_connect`. There is no Telegram command to turn it on; the former start command is ignored and never forwarded to the model.
+**Telegram stays off when OpenCode starts.** The connection only begins when you ask your agent to connect and it calls `telegram_connect`. There is no Telegram command to turn it on; `/start` and `/help` show the connection guide while the bridge is active; they cannot start an inactive bridge.
 
 ## Features
 
@@ -10,7 +10,7 @@ Control a running OpenCode session from Telegram with your own bot. Messages are
 - **Allowlist security.** Only configured Telegram user IDs or chat IDs can control the session; everything else is rejected. One-time pairing codes are supported when no allowlist is configured.
 - **Full session control.** List, switch, create, and rename sessions; list and switch models; abort running work.
 - **Permissions and questions in chat.** Approve, always-allow, or deny tool permissions and answer agent questions directly from Telegram, including inline buttons.
-- **Local credentials only.** The bot token and your user ID live in a local env file; nothing is uploaded anywhere.
+- **Local credentials only.** The bot token and your user ID live in a local env file; the token is sent only to Telegram for authentication. Prompts and responses pass through Telegram and the configured OpenCode model provider.
 
 ## System requirements
 
@@ -32,11 +32,11 @@ These are required only when building or testing this repository from source:
 
 ## Platform support
 
-The plugin uses only Node.js built-ins (`node:fs`, `node:os`, `node:path`, `node:http`) and the OpenCode plugin/SDK API. There is no platform-specific code:
+The plugin uses only Node.js built-ins (`node:fs`, `node:os`, `node:path`, `node:crypto`) and the OpenCode plugin/SDK API. There is no platform-specific code:
 
 - The Telegram transport is plain HTTPS long polling, identical on Windows, WSL, Linux, and macOS.
 - The config file is resolved through `os.homedir()` (`~/.config/opencode/telegram.env`), so it is correct on every platform.
-- The bot poll lock lives under the per-user config directory and works on all supported platforms.
+- The bot poll lock lives in the operating system temporary directory (`os.tmpdir()`) and works on all supported platforms.
 
 ## Install in native Windows OpenCode
 
@@ -50,7 +50,7 @@ notepad "$env:USERPROFILE\.config\opencode\opencode.json"
 ```json
 {
   "$schema": "https://opencode.ai/config.json",
-  "plugin": ["opencode-telegram-connect@1.0.2"]
+  "plugin": ["opencode-telegram-connect@1.0.3"]
 }
 ```
 
@@ -59,7 +59,7 @@ Keep any other settings and plugins in the file. OpenCode downloads and installs
 Optionally install the package globally to get the `opencode-telegram-user-id` helper command:
 
 ```powershell
-npm install -g opencode-telegram-connect@1.0.2
+npm install -g opencode-telegram-connect@1.0.3
 ```
 
 See also the [OpenCode plugin documentation](https://opencode.ai/docs/plugins/).
@@ -74,7 +74,7 @@ nano ~/.config/opencode/opencode.json
 opencode
 ```
 
-If your global config is `opencode.jsonc`, that file takes precedence - add the entry to its `plugin` array and check the effective list with `opencode debug config`. Pinning a version (e.g. `opencode-telegram-connect@1.0.2`) is recommended; the bare `latest` spec is cached permanently on first install.
+If your global config is `opencode.jsonc`, that file takes precedence - add the entry to its `plugin` array and check the effective list with `opencode debug config`. Pinning a version (e.g. `opencode-telegram-connect@1.0.3`) is recommended; an explicit version makes upgrades deliberate and avoids relying on cache refresh behavior.
 
 ## Uninstall
 
@@ -125,7 +125,7 @@ Save the file exactly as `telegram.env`, not `telegram.env.txt`.
 Keep the Telegram connection off in OpenCode. After you have privately sent your bot `Hallo`, run:
 
 ```sh
-npx --yes --package=opencode-telegram-connect@1.0.2 opencode-telegram-user-id
+npx --yes --package=opencode-telegram-connect@1.0.3 opencode-telegram-user-id
 ```
 
 The helper reads the token from your file and prints the user IDs of pending messages, for example `DeinName: TELEGRAM_USER=123456789`. It sends no message and never prints the token. If several people are listed, take your own ID. If nothing is listed, send `Hallo` again and repeat. No other application may poll this bot while you do this.
@@ -198,7 +198,7 @@ You first receive the session ID and then the model answer. The model works with
 
 For multiple questions: `/answer <id> answer one || answer two`. For multi-select: `Option A; Option B`. For simple choice questions and permissions you can use the inline buttons sent along.
 
-Other slash commands are forwarded to OpenCode as text; they do not automatically execute an OpenCode slash command. The removed start command is explicitly excluded from this.
+Other slash commands are forwarded to OpenCode as text; they do not automatically execute an OpenCode slash command. `/start` and `/help` are handled locally and never sent to the model.
 
 ### Turning Telegram off completely
 
@@ -210,6 +210,10 @@ This stops polling and releases the bot lock. `/disconnect` in Telegram only rem
 
 After restarting OpenCode you must connect again. Only one OpenCode instance can be connected to the same bot at a time. Other instances do not take over the bot automatically. Disconnect the previous instance, then ask the desired agent to connect.
 
+## Automatic connection guide
+
+After `telegram_connect`, the bridge sends the complete guide to configured users/chats and existing chat bindings. Users must have messaged the bot first and must not have blocked it. Delivery failures are reported by the connect tool; the bridge stays usable. Without static allowlists, the guide is sent after successful `/pair <code>`. Send `/start` or `/help` to display it again while connected.
+
 ## Configuration
 
 Existing environment variables take precedence. Accepted names:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-telegram-connect",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Native OpenCode plugin to securely control sessions from Telegram.",
   "type": "module",
   "main": "./src/index.js",

package/src/telegram.js

@@ -1,6 +1,7 @@
 const MAX_TELEGRAM_TEXT = 4096;
 
 export function splitTelegramText(text, limit = MAX_TELEGRAM_TEXT) {
+  if (!Number.isInteger(limit) || limit < 2) throw new Error("Text limit must be an integer of at least 2");
   const value = String(text ?? "");
   if (value.length <= limit) return [value];
   const chunks = [];
@@ -9,8 +10,9 @@ export function splitTelegramText(text, limit = MAX_TELEGRAM_TEXT) {
     let cut = rest.lastIndexOf("\n", limit);
     if (cut < Math.floor(limit * 0.6)) cut = rest.lastIndexOf(" ", limit);
     if (cut < Math.floor(limit * 0.6)) cut = limit;
+    if (/[\uD800-\uDBFF]/.test(rest[cut - 1]) && /[\uDC00-\uDFFF]/.test(rest[cut])) cut--;
     chunks.push(rest.slice(0, cut));
-    rest = rest.slice(cut).replace(/^\n/, "");
+    rest = rest.slice(cut);
   }
   if (rest) chunks.push(rest);
   return chunks;