clawgram 2.7.0 → 2.8.0

package/dist/channel.js

@@ -233,6 +233,20 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
         },
         capabilities: CHANNEL_CAPABILITIES,
         agentPrompt: {
+            // Core injects its `## Reactions` section only when this returns a
+            // level. Without it the prompt never mentions reactions, and the agent
+            // treats the `react` action as one more entry in a 106-property schema:
+            // she used it when asked outright in a DM and never once on her own.
+            reactionGuidance: ({ cfg, accountId }) => {
+                const resolvedAccountId = (0, helpers_1.resolveConfiguredAccountId)(cfg, accountId);
+                const account = resolvedAccountId
+                    ? cfg?.channels?.[constants_1.CHANNEL_ID]?.accounts?.[resolvedAccountId]
+                    : undefined;
+                const level = (0, reactions_1.resolveAgentReactionGuidance)(account?.reactionLevel);
+                // "clawgram" is our plugin id; the section reads "Reactions are
+                // enabled for <label>", and the label is the platform people see.
+                return level ? { level, channelLabel: "Telegram" } : undefined;
+            },
             messageToolHints: () => [
                 "Use clawgram to send Telegram replies from the connected personal account.",
                 "When replying in the current Telegram chat, omit `to`/`target` and clawgram will send to the current conversation automatically.",
@@ -781,7 +795,16 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                                     // A suppressed silent reply legitimately delivers nothing, so
                                     // this fallback fires right after it. Without the same check
                                     // the token would be read back from the transcript and sent.
-                                    const visibleFallbackText = fallbackText ? (0, helpers_1.stripSilentReplyToken)(fallbackText) : "";
+                                    //
+                                    // TTS markup needs the same treatment for the same reason:
+                                    // core strips it on the normal reply path, but this text comes
+                                    // straight out of the transcript. On 2026-08-08 a group got
+                                    // `[[tts:text]]Привет, Вася!…[[/tts:text]]` verbatim. The
+                                    // spoken words are kept — a synthesis that did not happen
+                                    // should degrade to readable text, not to markup.
+                                    const visibleFallbackText = fallbackText
+                                        ? (0, helpers_1.stripTtsDirectives)((0, helpers_1.stripSilentReplyToken)(fallbackText))
+                                        : "";
                                     if (fallbackText && !visibleFallbackText) {
                                         log?.info?.("clawgram skipping silent transcript fallback", {
                                             accountId,
@@ -1634,25 +1657,32 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                 }
                 actionLog.info("clawgram outbound sendMedia", {
                     accountId: ctx.accountId,
-                    to: ctx.to,
+                    rawTo: ctx.to,
                     replyToId: ctx.replyToId ?? null,
                     threadId: ctx.threadId ?? null,
                     filePath: ctx.filePath ?? null,
                     mediaUrl: ctx.mediaUrl ?? null,
                     hasText: Boolean(ctx.text),
                     hasCaption: Boolean(ctx.caption),
+                    asVoice: ctx.audioAsVoice === true,
                 });
                 const file = ctx.filePath ?? ctx.mediaUrl;
                 if (!file) {
                     throw new Error("clawgram: sendMedia requires filePath or mediaUrl");
                 }
                 const messageThreadId = parseOptionalThreadId(ctx.threadId);
+                // Same normalization `sendText` does two functions up. Without it the
+                // channel prefix reaches peer resolution and the send throws — which is
+                // exactly how a synthesized group reply died on 2026-08-08, silently
+                // enough that the transcript fallback posted it as raw text instead.
+                const target = (0, helpers_1.normalizeOutboundTarget)(ctx.to);
                 const sent = await gram.sendMedia({
-                    target: ctx.to,
+                    target,
                     file,
                     caption: ctx.caption ?? ctx.text,
                     replyToMessageId: (0, helpers_1.resolveReplyToMessageIdForTarget)(ctx.to, ctx.replyToId),
                     messageThreadId,
+                    asVoice: ctx.audioAsVoice === true,
                 });
                 actionLog.info("clawgram outbound sendMedia completed", {
                     accountId: ctx.accountId,

package/dist/helpers.js

@@ -16,6 +16,7 @@ exports.resolveActionTarget = resolveActionTarget;
 exports.resolveReplyToMessageIdForTarget = resolveReplyToMessageIdForTarget;
 exports.readMessageText = readMessageText;
 exports.readVoiceNoteFlag = readVoiceNoteFlag;
+exports.stripTtsDirectives = stripTtsDirectives;
 exports.resolveAllowFrom = resolveAllowFrom;
 exports.resolveGroupPolicy = resolveGroupPolicy;
 exports.resolveGroups = resolveGroups;
@@ -194,6 +195,28 @@ function resolveReplyToMessageIdForTarget(rawTarget, replyToId) {
     }
     return undefined;
 }
+/**
+ * Разметка синтеза речи, которая не должна доехать до человека.
+ *
+ * Core вырезает `[[tts:...]]` из видимого текста сам, но только на штатном
+ * пути ответа. Аварийный путь (`readLatestAssistantFallbackFromTranscript`)
+ * читает сырой текст из стенограммы, поэтому 2026-08-08 в групповой чат
+ * ушло `[[tts:text]]Привет, Вася!…[[/tts:text]]` как есть.
+ *
+ * Блок `[[tts:text]]…[[/tts:text]]` РАЗВОРАЧИВАЕТСЯ, а не удаляется: внутри
+ * лежит то, что агент собирался сказать. Если синтез не состоялся, человек
+ * должен получить эти слова текстом — деградация в читаемое, а не в мусор
+ * и не в пустоту.
+ */
+const TTS_TEXT_BLOCK = /\[\[tts:text\]\]([\s\S]*?)\[\[\/tts:text\]\]/gi;
+const TTS_DIRECTIVE = /\[\[\s*\/?\s*(?:tts:[^\]]*|audio_as_voice)\s*\]\]/gi;
+function stripTtsDirectives(text) {
+    return text
+        .replace(TTS_TEXT_BLOCK, (_match, spoken) => spoken)
+        .replace(TTS_DIRECTIVE, "")
+        .replace(/[ \t]{2,}/g, " ")
+        .trim();
+}
 /**
  * Whether an outbound file should become a Telegram voice message.
  *

package/dist/reactions.js

@@ -11,7 +11,47 @@
  * tested without a Telegram connection.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.resolveAgentReactionGuidance = resolveAgentReactionGuidance;
 exports.parseReactionParams = parseReactionParams;
+/**
+ * How chatty the agent may be with reactions, as core understands it.
+ *
+ * Core injects a `## Reactions` section into the system prompt only when a
+ * channel returns a level from `agentPrompt.reactionGuidance`. Return nothing
+ * and the prompt never mentions reactions at all — which is what happened
+ * here until 2.8.0: the `react` action existed, the agent had it, and no line
+ * of the prompt suggested using it.
+ *
+ * Levels and fallbacks mirror the bundled Telegram channel so the two behave
+ * the same for the same config:
+ *
+ * - `off`, `ack` — no agent reactions (`ack` is the "seen it" emoji core sends
+ *   by itself, which is a different feature);
+ * - `minimal` — react sparingly; the default when nothing is configured;
+ * - `extensive` — react whenever it feels natural.
+ *
+ * An invalid value yields no guidance rather than a guess: a typo turning a
+ * work chat chatty is worse than a typo turning it quiet.
+ */
+function resolveAgentReactionGuidance(value) {
+    if (value === undefined || value === null) {
+        return "minimal";
+    }
+    if (typeof value !== "string") {
+        return undefined;
+    }
+    const level = value.trim();
+    if (!level) {
+        return "minimal";
+    }
+    if (level === "minimal" || level === "extensive") {
+        return level;
+    }
+    if (level === "off" || level === "ack") {
+        return undefined;
+    }
+    return undefined;
+}
 /** Accepts the boolean and the string a JSON-ish caller may send for it. */
 function readBooleanFlag(value) {
     return value === true || value === "true";

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "clawgram",
   "name": "Clawgram",
   "description": "Clawgram — personal Telegram (MTProto userbot) channel for OpenClaw. Your AI assistant reads and responds as you.",
-  "version": "2.7.0",
+  "version": "2.8.0",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,
@@ -326,6 +326,16 @@
                   "type": "string",
                   "description": "Where joins observed for this account are journalled. Defaults to a per-account file under the OpenClaw state directory."
                 },
+                "reactionLevel": {
+                  "type": "string",
+                  "enum": [
+                    "off",
+                    "ack",
+                    "minimal",
+                    "extensive"
+                  ],
+                  "description": "How freely the agent may leave emoji reactions (2.8.0). Core injects its `## Reactions` prompt section only for `minimal` and `extensive`; `off` and `ack` leave the prompt silent about reactions, and the agent then effectively never reacts on its own. Absent means `minimal`. Mirrors the bundled Telegram channel's reactionLevel."
+                },
                 "replyParseMode": {
                   "type": "string",
                   "enum": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clawgram",
-  "version": "2.7.0",
+  "version": "2.8.0",
   "description": "Clawgram — personal Telegram (MTProto userbot) channel for OpenClaw. Your AI assistant reads and responds as you.",
   "main": "./dist/index.js",
   "scripts": {