clawgram 2.3.2 → 2.4.0

package/dist/channel.js

@@ -121,6 +121,11 @@ const createChannelPlugin = (runtimes) => {
                     enabled: account?.enabled,
                     accountId,
                     proxy: (0, proxy_config_1.resolveProxyConfig)(account?.proxy),
+                    // Field-by-field construction means every new account setting has to
+                    // be listed here as well: 2.3.1 shipped replyParseMode read by the
+                    // client from a config object this function had already stripped it
+                    // from, so the setting validated, deployed and did nothing.
+                    replyParseMode: account?.replyParseMode,
                 };
             },
         },
@@ -465,6 +470,12 @@ const createChannelPlugin = (runtimes) => {
                                 MessageSidFull: normalized.messageId,
                                 Timestamp: normalized.timestamp,
                                 ReplyToId: normalized.replyToMessageId,
+                                // Core renders these itself as `[Replying to: "…"]` ahead of the
+                                // user body — it keys off Provider being "telegram", which is set
+                                // below. Without them a highlighted reply reaches the agent as
+                                // bare text, and the fragment the person pointed at is lost.
+                                ReplyToQuoteText: normalized.replyQuoteText,
+                                ReplyToIsQuote: normalized.replyIsQuote,
                                 MessageThreadId: normalized.messageThreadId,
                                 NativeChannelId: normalized.chatId,
                                 OriginatingChannel: "clawgram",
@@ -741,6 +752,10 @@ const createChannelPlugin = (runtimes) => {
                                     SenderUsername: normalized.senderUsername,
                                     SenderName: normalized.senderDisplay,
                                     ReplyToId: normalized.replyToMessageId,
+                                    // Same reason as the group path: highlighted replies happen in
+                                    // direct messages too, and the fragment is not part of the text.
+                                    ReplyToQuoteText: normalized.replyQuoteText,
+                                    ReplyToIsQuote: normalized.replyIsQuote,
                                     NativeChannelId: normalized.chatId,
                                 },
                                 deliver: async (payload) => {

package/dist/history.js

@@ -227,6 +227,14 @@ function resolveSenderDisplay(msg) {
         return joined;
     return readSender(msg, "title") ?? readSender(msg, "username");
 }
+/**
+ * Same rule as the inbound path (`normalize.ts`): the text is the evidence,
+ * not the `quote` flag, and blank text means no highlight.
+ */
+function resolveHistoryReplyQuote(msg) {
+    const raw = msg?.replyTo?.quoteText ?? msg?.quoteText;
+    return typeof raw === "string" && raw.trim() ? raw : undefined;
+}
 /**
  * Deliberately drops `raw`. Inbound events carry it because the runtime may need
  * the original object; history is read straight into a model's context, where an
@@ -258,6 +266,7 @@ function normalizeHistoryMessage(msg, fallbackChatId) {
         timestamp,
         sentAt: timestamp === undefined ? undefined : new Date(timestamp * 1000).toISOString(),
         replyToMessageId: toStringId(msg?.replyTo?.replyToMsgId) ?? toStringId(msg?.replyToMsgId),
+        replyQuoteText: resolveHistoryReplyQuote(msg),
         messageThreadId: toStringId(msg?.replyTo?.replyToTopId) ?? toStringId(msg?.replyToTopId),
         media: (0, media_1.describeMedia)(msg?.media),
         isOutgoing: msg?.out === true,

package/dist/normalize.js

@@ -66,6 +66,21 @@ function resolveMessageThreadId(msg) {
     return (toStringId(msg?.replyTo?.replyToMsgId) ??
         toStringId(msg?.replyToMsgId));
 }
+/**
+ * The highlighted fragment of a reply, when there is one.
+ *
+ * Telegram sends the flag and the text separately, and clients in the wild are
+ * not consistent about the flag. The text is the evidence: if `quoteText` has
+ * content, a fragment was highlighted regardless of what `quote` says. Blank
+ * text is treated as no highlight rather than as an empty one.
+ */
+function resolveReplyQuote(msg) {
+    const raw = msg?.replyTo?.quoteText ?? msg?.quoteText;
+    const text = typeof raw === "string" && raw.trim() ? raw : undefined;
+    if (!text)
+        return {};
+    return { text, isQuote: true };
+}
 function normalizeTelegramEvent(event, accountId) {
     const msg = event?.message;
     if (!msg)
@@ -84,6 +99,7 @@ function normalizeTelegramEvent(event, accountId) {
     const replyToMessageId = toStringId(msg.replyTo?.replyToMsgId) ??
         toStringId(msg.replyToMsgId);
     const messageThreadId = resolveMessageThreadId(msg);
+    const replyQuote = resolveReplyQuote(msg);
     const text = typeof msg.message === "string"
         ? msg.message
         : typeof msg.text === "string"
@@ -116,6 +132,8 @@ function normalizeTelegramEvent(event, accountId) {
         messageId,
         text,
         replyToMessageId,
+        replyQuoteText: replyQuote.text,
+        replyIsQuote: replyQuote.isQuote,
         chatType,
         timestamp: toTimestamp(msg.date),
         isOutgoing: Boolean(msg.out),

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

package/package.json

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