clawgram 2.8.1 → 2.9.0

package/dist/channel.js

@@ -67,6 +67,14 @@ const helpers_1 = require("./helpers");
 const proxy_config_1 = require("./proxy-config");
 const constants_1 = require("./constants");
 const actionLog = (0, core_1.createSubsystemLogger)("channels/clawgram");
+/** Reads the configured reaction level for an account, tolerating a missing config. */
+function readAccountReactionLevel(cfg, accountId) {
+    const resolvedAccountId = (0, helpers_1.resolveConfiguredAccountId)(cfg, accountId);
+    if (!resolvedAccountId) {
+        return undefined;
+    }
+    return cfg?.channels?.[constants_1.CHANNEL_ID]?.accounts?.[resolvedAccountId]?.reactionLevel;
+}
 /**
  * Read scope as configured for the account. Left `undefined` when the key is
  * absent so `isChatReadable` can tell "not configured" from "configured empty" —
@@ -258,14 +266,25 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                 // 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.",
-                "Explicit targets may be @username, numeric Telegram user id, phone/contact resolvable by Telegram, group chat ids, or clawgram:<target>.",
-                "For Telegram forum topics, send to the group chat id and pass the topic id separately as `threadId`.",
-                "Use the `react` action to acknowledge a message with an emoji instead of sending a reply; pass an empty `emoji` (or `remove: true`) to take the reaction back.",
-                "Use the `chatInfo` action to learn what a chat is — title, type, member count, description, pinned message — instead of guessing from its id.",
-            ],
+            messageToolHints: ({ cfg, accountId } = {}) => {
+                const level = (0, reactions_1.resolveAgentReactionGuidance)(readAccountReactionLevel(cfg, accountId));
+                // Logged for the same reason reactionGuidance is: this path is the
+                // workaround for core skipping that hook, so "did our text reach the
+                // prompt" has to be answerable from the log rather than by inference.
+                actionLog.info("clawgram messageToolHints", {
+                    accountId: accountId ?? null,
+                    reactionLevel: level ?? null,
+                });
+                return [
+                    "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.",
+                    "Explicit targets may be @username, numeric Telegram user id, phone/contact resolvable by Telegram, group chat ids, or clawgram:<target>.",
+                    "For Telegram forum topics, send to the group chat id and pass the topic id separately as `threadId`.",
+                    "Use the `react` action to acknowledge a message with an emoji instead of sending a reply; pass an empty `emoji` (or `remove: true`) to take the reaction back.",
+                    "Use the `chatInfo` action to learn what a chat is — title, type, member count, description, pinned message — instead of guessing from its id.",
+                    ...(0, reactions_1.buildReactionHintLines)(level),
+                ];
+            },
             messageToolCapabilities: () => [
                 "clawgram can reply in the current Telegram conversation when no explicit target is provided.",
                 "clawgram can send text messages to direct chats and groups from the connected personal account.",

package/dist/reactions.js

@@ -11,6 +11,7 @@
  * tested without a Telegram connection.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.buildReactionHintLines = buildReactionHintLines;
 exports.resolveAgentReactionGuidance = resolveAgentReactionGuidance;
 exports.parseReactionParams = parseReactionParams;
 /**
@@ -33,6 +34,41 @@ exports.parseReactionParams = parseReactionParams;
  * 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.
  */
+/**
+ * The reaction guidance as prompt lines, carried by `messageToolHints`.
+ *
+ * Core has its own `## Reactions` section, but it only builds it when
+ * `params.config` is truthy in the prompt assembler — a condition our channel
+ * never satisfied: the hook logged zero invocations across live turns while
+ * the neighbouring `messageToolHints`, guarded only by the channel being
+ * resolved, is called every time.
+ *
+ * That condition lives in the minified `openclaw` dependency, so it is not
+ * ours to fix; patching `node_modules` would evaporate on the next update.
+ * The hints path is ours, reaches the same prompt, and does not depend on
+ * that diagnosis being right — if the hints arrive, so does the text.
+ *
+ * Wording follows core's own so behaviour stays the same if it ever starts
+ * calling the hook and both appear.
+ */
+function buildReactionHintLines(level) {
+    if (!level) {
+        return [];
+    }
+    const shared = [
+        "Use the `react` action for this: it leaves an emoji on a message without sending one.",
+        "A reaction is not a reply — you can react and still return NO_REPLY, and that is the point when someone names you but needs no answer.",
+    ];
+    return level === "minimal"
+        ? [
+            "Reactions are enabled for Telegram in MINIMAL mode. React ONLY when truly relevant: acknowledge an important request or confirmation, or show genuine sentiment sparingly. Do not react to routine messages or to your own replies. Guideline: at most 1 reaction per 5-10 exchanges.",
+            ...shared,
+        ]
+        : [
+            "Reactions are enabled for Telegram in EXTENSIVE mode. React liberally: acknowledge messages with a fitting emoji, show sentiment and personality, react to humour, notable events or good news, and use a reaction to confirm agreement. Guideline: react whenever it feels natural.",
+            ...shared,
+        ];
+}
 function resolveAgentReactionGuidance(value) {
     if (value === undefined || value === null) {
         return "minimal";

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.8.1",
+  "version": "2.9.0",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

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