appback-remoteagent 0.17.1 → 0.20.0

package/README.md

@@ -103,6 +103,8 @@ Current command surface implemented in `src/bot.ts`:
 | `/new` | Creates and binds a new session using the saved default mode in a new managed workspace |
 | `/switch <session>` | Rebinds this chat to an existing RemoteAgent session |
 | `/status` | Shows current session, workspace, provider, and sandbox state |
+| `/model [name]` | Lists selectable provider models or changes the current session model |
+| `/sandbox [codex <mode>]` | Lists Codex sandbox choices or changes the current session sandbox |
 | `/option retry <count>` | Sets the automatic continuation turn limit and persists it to `~/.remoteagent/.env` |
 | `/option timeout <seconds>` | Sets the provider execution timeout and persists it to `~/.remoteagent/.env` |
 | `/option intent <count>` | Sets retries for untagged intent-only provider replies and persists it to `~/.remoteagent/.env` |
@@ -110,6 +112,7 @@ Current command surface implemented in `src/bot.ts`:
 | `/state clear` | Clears the current session ledger without deleting the session |
 | `/state note <text>` | Adds an operator note to the session ledger |
 | `/bots` | Lists the currently configured Telegram bots |
+| `/macro [alias\|number]` | Lists stored macros or runs one against the current session |
 | `/bot add <token>` | Adds a conversation bot, restarts the runtime, and confirms the result after restart |
 | `/bot doctor` | Checks configured Telegram bots and removes bots that Telegram reports as permanently dead |
 | `/bot remove <username\|id>` | Removes a configured Telegram bot, restarts the runtime, and confirms the result after restart |
@@ -127,6 +130,8 @@ Current command surface implemented in `src/bot.ts`:
 | `/queue remove <id>` | Removes one waiting instruction by its `Q001`-style id |
 | `/queue del` | Removes the most recently queued instruction |
 
+Selection-oriented replies include Telegram inline buttons for sessions, models, macros, runtime option details, sandbox modes, queued instructions, and configured bot links. Text commands remain the canonical compatible interface. Callback actions use short-lived opaque IDs bound to the originating chat and user; they do not expose secrets or rely on visible list positions as internal identity. Selecting `danger-full-access` through a button requires a second confirmation.
+
 Multi-bot polling is tiered by recent activity and active provider work. See [docs/BOT_POLLING_POLICY.md](./docs/BOT_POLLING_POLICY.md).
 
 ### 2. Terminal control
@@ -313,6 +318,34 @@ remoteagent-start
 
 `remoteagent-install` seeds provider install/login hook paths into `~/.remoteagent/.env` automatically, so `/install codex` and `/install claude` work on a fresh machine without manual hook wiring.
 
+Register the first Telegram bot without editing `.env` manually:
+
+```bash
+remoteagent bot add
+remoteagent-start
+```
+
+The command validates the BotFather token, stores the bot configuration, and configures the numeric Telegram owner user ID. Tokens are entered through a hidden prompt by default.
+
+To move installation-wide `/secret` values to another PC, export and import a password-encrypted bundle:
+
+```bash
+# Old PC
+remoteagent secret export ~/remoteagent-secrets.ra-secrets
+
+# New PC
+remoteagent secret import ~/remoteagent-secrets.ra-secrets
+```
+
+See [CLI bootstrap and secret migration](./docs/CLI_BOOTSTRAP_AND_SECRET_MIGRATION.md) for the complete interactive and automation-safe commands.
+
+Selected Secret keys can also be returned to the current private Telegram chat as a compressed, encrypted bundle without exposing values to the provider:
+
+```text
+/secret set REMOTEAGENT_TRANSFER_PASSPHRASE a-long-private-passphrase
+/secret export REMOTEAGENT_TRANSFER_PASSPHRASE KEY_ONE KEY_TWO
+```
+
 For one-line installs on a fresh machine:
 
 ```bash

package/bin/remoteagent.js

@@ -1,2 +1,2 @@
 #!/usr/bin/env node
-import "../dist/index.js";
+import "../dist/cli.js";

package/dist/adapters/codex-adapter.js

@@ -115,10 +115,7 @@ export class CodexAdapter {
         }
         let text;
         try {
-            const event = JSON.parse(line);
-            text = event.type === "item.completed" && event.item?.type === "agent_message"
-                ? event.item.text?.trim()
-                : undefined;
+            text = this.extractEventAgentText(JSON.parse(line));
         }
         catch {
             // Ignore non-JSON stdout and let the normal final-response parser handle it.
@@ -128,6 +125,27 @@ export class CodexAdapter {
             await onProgress(text);
         }
     }
+    extractEventAgentText(event) {
+        if (!event || typeof event !== "object") {
+            return undefined;
+        }
+        const record = event;
+        if (record.type === "item.completed" && record.item?.type === "agent_message") {
+            return record.item.text?.trim();
+        }
+        if (record.type === "event_msg" && record.payload?.type === "agent_message") {
+            return (record.payload.message ?? record.payload.text)?.trim();
+        }
+        if (record.type === "response_item" && record.payload?.type === "message") {
+            const text = record.payload.content
+                ?.filter((item) => item.type === "output_text" && typeof item.text === "string")
+                .map((item) => item.text)
+                .join("\n")
+                .trim();
+            return text || record.payload.text?.trim();
+        }
+        return undefined;
+    }
     extractThreadId(stdout) {
         for (const line of stdout.split(/\r?\n/)) {
             if (!line.startsWith("{")) {