clawgram 2.7.1 → 2.8.1

package/dist/channel.js

@@ -233,6 +233,31 @@ 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);
+                // Logged because "the hook returns the right thing" and "the prompt
+                // gained a Reactions section" turned out to be different questions:
+                // on 2.8.0 the first was verifiable by hand on the server while the
+                // prompt stayed byte-identical. Without this line there is no way to
+                // tell a hook core never calls from a hook that answers undefined.
+                actionLog.info("clawgram reactionGuidance", {
+                    accountId: resolvedAccountId ?? null,
+                    requestedAccountId: accountId ?? null,
+                    configuredLevel: typeof account?.reactionLevel === "string" ? account.reactionLevel : null,
+                    level: level ?? null,
+                });
+                // "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.",

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.1",
+  "version": "2.8.1",
   "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.1",
+  "version": "2.8.1",
   "description": "Clawgram — personal Telegram (MTProto userbot) channel for OpenClaw. Your AI assistant reads and responds as you.",
   "main": "./dist/index.js",
   "scripts": {