appback-remoteagent 0.13.7 → 0.13.10

package/dist/bot.js

@@ -58,13 +58,11 @@ const REPORT_PROTOCOL_PROMPT = [
     "Do not say 'I will continue' or 'I can continue after you do X' unless the first line is REPORT:blocked.",
     "After the first line, write only the user-facing report.",
     "Do not stop at intent like 'I will' or 'I am going to'. Do the work first, then report progress/result, or report blocked.",
-    "Do not claim that a Telegram message or file was sent unless RemoteAgent explicitly confirmed that delivery step.",
     "If REPORT:result claims code, DB, deploy, commit, push, file delivery, or verification work is complete, include concrete evidence such as file paths, commands, logs, commit IDs, digests, or line references.",
-    "If you want RemoteAgent to send a file, include a separate line exactly like: TELEGRAM_FILE: /absolute/path/to/file",
-    "Do not use removed local reporting scripts for Telegram delivery.",
-    "Do not use raw Telegram tokens or TELEGRAM_* environment variables.",
-    "Telegram sends are allowed only when the user explicitly instructed that flow and the bot token is retrieved through `node \"$REMOTEAGENT_SECRET_BIN\" get <KEY>`. Never print or persist the token.",
-    "Do not claim Telegram message delivery unless RemoteAgent handled `TELEGRAM_FILE` delivery or you include concrete API response evidence from an explicit secret-managed Telegram send.",
+    "RemoteAgent owns conversational delivery: return text normally and RemoteAgent sends it to the current incoming chat.",
+    "RemoteAgent owns attachment delivery: include a separate line exactly like `TELEGRAM_FILE: /absolute/path/to/file` and RemoteAgent sends that file to the current incoming chat.",
+    "Product/service Telegram notifications are product code behavior; use the project's secret/config path and keep tokens out of output.",
+    "Use project secrets or `node \"$REMOTEAGENT_SECRET_BIN\" get <KEY>` for sensitive runtime values, and never print secret values.",
     "REMOTEAGENT_SESSION_ID and REMOTEAGENT_PUBLIC_SESSION_ID are available during provider execution. For cron, persist the literal public session id in the cron command instead of assuming the env will still exist later.",
 ].join("\n");
 const RECOGNIZED_COMMANDS = new Set([
@@ -2083,12 +2081,8 @@ async function normalizeTelegramDelivery(chunks) {
         }
         return kept.join("\n").trim();
     }));
-    const nonEmptyChunks = normalizedChunks.filter(Boolean);
-    if (documents.size === 0 && nonEmptyChunks.some((chunk) => mentionsTelegramDeliveryClaim(chunk))) {
-        throw new Error("\ubaa8\ub378\uc774 \ud154\ub808\uadf8\ub7a8 \uc804\uc1a1 \uc644\ub8cc\ub97c \uc8fc\uc7a5\ud588\uc9c0\ub9cc, RemoteAgent\uac00 \ud655\uc778\ud55c \ud30c\uc77c \uc804\uc1a1 \uc9c0\uc2dc(`TELEGRAM_FILE: /absolute/path/to/file`)\ub294 \ud3ec\ud568\ub418\uc9c0 \uc54a\uc558\uc2b5\ub2c8\ub2e4. \ud30c\uc77c\uc744 \ubcf4\ub0b4\ub824\uba74 \ud574\ub2f9 \ud615\uc2dd\uc73c\ub85c \uc808\ub300 \uacbd\ub85c\ub97c \uba85\uc2dc\ud574\uc57c \ud569\ub2c8\ub2e4.");
-    }
     return {
-        chunks: nonEmptyChunks,
+        chunks: normalizedChunks.filter(Boolean),
         documents: [...documents.values()],
     };
 }
@@ -2104,9 +2098,6 @@ async function isReadableTelegramDocument(filePath) {
         return false;
     }
 }
-function mentionsTelegramDeliveryClaim(text) {
-    return /(telegram).*(sent|delivered|delivery)|((sent|delivered|delivery).*(telegram))/i.test(text);
-}
 async function sendTelegramDocuments(botToken, chatId, documents) {
     for (const document of documents) {
         await sendTelegramDocument(botToken, chatId, document);

package/dist/services/agent-memory-service.js

@@ -325,7 +325,9 @@ export class AgentMemoryService {
                 "- Treat the user message as the active instruction unless the user explicitly says otherwise.",
                 "- RemoteAgent state is guidance only; never refuse work because a TODO is missing.",
                 "- Use the workspace/memory/docs pointers before searching broadly.",
-                "- Do not claim external delivery, dashboard access, deployment, or file transfer without RemoteAgent-confirmed evidence.",
+                "- Do not claim external delivery, dashboard access, deployment, or file transfer without concrete evidence.",
+                "- RemoteAgent sends normal provider text and TELEGRAM_FILE attachments to the current incoming chat.",
+                "- Product/service Telegram notifications belong to product code and should use the project's secret/config path. Never print tokens.",
                 "- If the same action or progress repeats 3 times, stop, mark the blocker, and report the exact blocker.",
                 "- A final report must include concrete evidence: changed files, relevant line references, git diff/status, command output, or log path.",
             ].join("\n"),

package/docs/ARCHITECTURE.md

@@ -56,6 +56,16 @@ Responsibilities:
 - accept attachments and route them to the active session
 - gate privileged commands such as remote shell
 
+### Telegram delivery ownership
+
+RemoteAgent owns delivery for the conversation it is handling.
+
+- normal provider text is sent by RemoteAgent to the current incoming bot and chat
+- provider attachments are sent by RemoteAgent when the provider includes `TELEGRAM_FILE: /absolute/path/to/file`
+- the provider does not choose a bot token or chat id for RemoteAgent replies or files
+- product or service code Telegram notifications are separate application behavior and should use that project's own secret/config path
+- Telegram tokens and other credentials must stay in secrets/config and must not be printed in provider output
+
 ### Telegram Mini App layer
 
 Responsibilities:
@@ -167,4 +177,4 @@ Still improving:
 - hosted multi-tenant control plane
 - account pooling or resale
 - pretending RemoteAgent is the official Codex or Claude desktop product
-- treating Telegram itself as the execution backend
+- treating Telegram itself as the execution backend

package/docs/OPERATIONS.md

@@ -161,8 +161,9 @@ As of the latest stabilization work:
 - Telegram image download works
 - files are saved under `/home/au2223/.remoteagent/uploads/telegram/...`
 - duplicate runtime startup has been blocked
-- cross-bot direct Telegram token leakage to provider subprocesses has been blocked
-- official runtime-mediated file sending is available only through confirmed RemoteAgent transfer paths
+- RemoteAgent-mediated file sending uses `TELEGRAM_FILE: /absolute/path/to/file`
+- RemoteAgent sends conversation replies and `TELEGRAM_FILE` attachments only to the current incoming bot and chat
+- product/service Telegram notifications are not RemoteAgent conversation delivery; they belong in that project's code and should use that project's secret/config path
 
 Remaining work is still needed on attachment response policy and richer file UX.
 The transport/runtime stability issue and the user-facing attachment response quality issue are separate concerns.
@@ -176,6 +177,6 @@ The deeper issues were runtime ownership and transport discipline:
 - service-managed and manually-started processes overlapped
 - PID state and actual live processes diverged
 - Telegram responses could come from an unexpected process generation
-- provider subprocesses had to be prevented from directly using Telegram bot tokens
+- RemoteAgent conversation delivery needed a single current incoming bot/chat owner
 
-The single-instance lock, `systemd`-first lifecycle, and runtime-mediated file transfer rules were added specifically to stop that class of bug from recurring.
+The single-instance lock, `systemd`-first lifecycle, and runtime-owned conversation delivery rules were added specifically to stop that class of bug from recurring.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "appback-remoteagent",
-  "version": "0.13.7",
+  "version": "0.13.10",
   "description": "Personal installable session server for continuing local AI work across PC and Telegram",
   "license": "MIT",
   "type": "module",