clawgram 2.12.1 → 2.13.1

package/dist/channel.js

@@ -1305,7 +1305,11 @@ const createChannelPlugin = (runtimes, pluginRuntime) => {
                 };
             },
             extractToolSend: ({ args }) => (0, tool_send_1.extractToolSend)(args, "sendMessage"),
-            handleAction: async ({ action, params, cfg, accountId, dryRun, toolContext }) => {
+            handleAction: async ({ action, params, cfg, accountId, dryRun: dryRunFlag, toolContext }) => {
+                // Core passes the flag beside `params`; callers write it inside.
+                // Both count, because a rehearsal flag that is silently ignored puts
+                // a real message in a real chat — twice, so far (2.13.1).
+                const dryRun = (0, helpers_1.resolveDryRun)(dryRunFlag, params);
                 // `read` is what OpenClaw core dispatches (`openclaw message read`,
                 // MCP `messages_read`). `list` is accepted as a synonym so a caller that
                 // guessed the other obvious name is not silently refused.
@@ -1783,7 +1787,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,8 @@ exports.resolveSenderProfile = resolveSenderProfile;
 exports.resolveSenderProfileWithTimeout = resolveSenderProfileWithTimeout;
 exports.normalizeParseMode = normalizeParseMode;
 exports.resolveReplyParseMode = resolveReplyParseMode;
+exports.resolveOutboundParseMode = resolveOutboundParseMode;
+exports.resolveDryRun = resolveDryRun;
 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 +579,48 @@ function resolveReplyParseMode(cfg, accountId) {
     const account = channel?.accounts?.[accountId] ?? channel;
     return normalizeParseMode(account?.replyParseMode);
 }
+/**
+ * Whether this call is a rehearsal, from either position the flag can arrive.
+ *
+ * Core passes `dryRun` as a sibling of `params`. Callers put it inside
+ * `params`, next to `to` and `text`, because that is where every other
+ * parameter lives — and there it used to be read by nobody: the flag vanished
+ * and the send happened for real.
+ *
+ * That is the worst possible failure mode for a safety flag, and it has cost
+ * two irreversible messages in a work chat (2026-08-08, note 0066; and
+ * 2026-08-10 at 02:49 UTC, a bare "ping" the agent then could not delete,
+ * because this channel has no delete action). Either position now counts, and
+ * a disagreement resolves toward **not** sending: a caller who wrote
+ * "dry run" anywhere meant it somewhere.
+ */
+function resolveDryRun(dryRun, params) {
+    const fromParams = params?.dryRun;
+    return dryRun === true || dryRun === "true" || fromParams === true || fromParams === "true";
+}
+/**
+ * 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/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.1",
+  "version": "2.13.1",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

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