clawgram 2.12.0 → 2.13.0

package/dist/channel.js

@@ -1783,7 +1783,10 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                 const replyToId = (0, param_readers_1.readStringOrNumberParam)(params, "replyToId") ?? (0, param_readers_1.readStringOrNumberParam)(params, "replyTo");
                 const threadId = (0, param_readers_1.readStringOrNumberParam)(params, "threadId");
                 const messageThreadId = parseOptionalThreadId(threadId);
-                const parseMode = (0, helpers_1.normalizeParseMode)(params?.parseMode);
+                // Omitting parseMode inherits the account's configured mode rather
+                // than falling back to plain text (2.13.0): an account set to `html`
+                // used to render replies as HTML and these sends as raw markup.
+                const parseMode = (0, helpers_1.resolveOutboundParseMode)(params, cfg, (0, helpers_1.resolveConfiguredAccountId)(cfg, accountId) ?? accountId ?? "default");
                 actionLog.info("clawgram handleAction send", {
                     requestedAccountId: accountId,
                     dryRun: dryRun === true,

package/dist/helpers.js

@@ -37,6 +37,7 @@ exports.resolveSenderProfile = resolveSenderProfile;
 exports.resolveSenderProfileWithTimeout = resolveSenderProfileWithTimeout;
 exports.normalizeParseMode = normalizeParseMode;
 exports.resolveReplyParseMode = resolveReplyParseMode;
+exports.resolveOutboundParseMode = resolveOutboundParseMode;
 const node_fs_1 = require("node:fs");
 const node_path_1 = __importDefault(require("node:path"));
 const core_1 = require("openclaw/plugin-sdk/core");
@@ -577,3 +578,29 @@ function resolveReplyParseMode(cfg, accountId) {
     const account = channel?.accounts?.[accountId] ?? channel;
     return normalizeParseMode(account?.replyParseMode);
 }
+/**
+ * Parse mode for the `send` action (2.13.0).
+ *
+ * The per-call parameter still wins — a caller that knows its text is markdown
+ * has to be able to say so, and `parseMode: ""` still means "exactly as typed".
+ * What changed is the default: an omitted parameter now inherits the account's
+ * configured mode instead of silently sending plain text.
+ *
+ * Before this, the two send paths disagreed. An account set to `html` rendered
+ * replies as HTML and tool-driven sends as plain text, so an answer written in
+ * markup arrived with its markup showing — which is what happened on
+ * 2026-08-09 at 22:30 UTC, in a work chat, to a long answer. Two sends half an
+ * hour earlier had passed `parseMode` by hand and looked right; that is the
+ * tell, not the reassurance. Correctness that depends on remembering a
+ * parameter on every call is correctness that will lapse.
+ */
+function resolveOutboundParseMode(params, cfg, accountId) {
+    const raw = params?.parseMode;
+    // An explicitly empty value is a decision, not an omission: send it raw.
+    if (raw === "" || raw === null) {
+        return undefined;
+    }
+    return raw === undefined
+        ? resolveReplyParseMode(cfg, accountId)
+        : normalizeParseMode(raw);
+}

package/dist/silent-reaction.js

@@ -46,8 +46,19 @@ function buildEmojiSystemPrompt(appetite, allowed) {
         `- the message is about producing something written — a text, a reply, a document, a draft → ✍`,
         "Otherwise match the mood: a joke gets something amused, bad news something",
         "sympathetic, an achievement something celebratory.",
-        "Answer NONE when the message is conflictual, heavy, or discusses a person's",
-        "performance — a reaction there reads as a verdict on someone.",
+        "Answer NONE when the message is conflictual or heavy, or when it judges",
+        "SOMEONE ELSE's work or behaviour — a reaction there reads as a verdict on",
+        "that person.",
+        // Without this the NONE rule swallowed the praise rule: "молодец тина" is
+        // literally a statement about someone's performance, the model applied the
+        // rule as written, and answered NONE to being praised. The carve-out
+        // exists in the assistant's own rules — the ban on judging people protects
+        // others, not itself — and had to be repeated here.
+        "That restraint protects other people and does NOT apply to the assistant",
+        "itself. Praise, teasing, thanks or criticism aimed at the assistant is",
+        "exactly what the fixed answers above are for: being called clever, useful",
+        "or 'молодец' is praise → ❤, not a verdict on a third party.",
+        "When a fixed answer applies, it wins over the mood rule.",
     ];
     return appetite === "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.12.0",
+  "version": "2.13.0",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

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