@relaymessenger/openclaw-plugin 0.4.7-staging.40 → 0.4.7-staging.41

package/contracts/relay-v1.lock.json

@@ -7,8 +7,8 @@
   },
   "relaySdk": {
     "package": "@relaymessenger/sdk",
-    "version": "0.3.6-staging.47",
-    "integrity": "sha512-CI67lgtiuYyhSwuttqXF6x07OC9fDwTIpT3eCZPiqHGxWDo6Tx/zNmAAUzEDcw9ExoGOHP2VXnIlcDFMlQrslw==",
+    "version": "0.3.6-staging.48",
+    "integrity": "sha512-1IZ3eLkdNGi6u8PzRBGET40IwxiDLBb3tuQG9V+RXUfyizw5AiWKF1vWg0pm2gz7jQsSFwyMWlyGynNOZZOnOQ==",
     "operationsSha256": "3e09d345c249709d942d2efb89ed7e84934c19552767d8f4438eb086dd917e1c",
     "workspaceOpenapiSha256": "44d3202de07206707c8914c37029abc365c144be4245e677574210d2a1cf6f41",
     "usedOperations": [

package/dist/src/dispatch.js

@@ -60,8 +60,10 @@ async function readReplyTarget(params) {
  * OpenClaw's own reply context, `supplemental.quote`, which it renders to the
  * model as "Reply target of current user message" (id, sender, body), as its
  * Telegram channel fills it from Telegram's `reply_to_message`. A reply names
- * one bubble: when the target has more than one part, only the swiped part is
- * quoted, the rule Relay's iOS app uses to draw the quote.
+ * one bubble: a multipart target is narrowed to the swiped part, the rule
+ * Relay's iOS app uses to draw the quote (the SDK's `replyTargetParts`); a
+ * tap or a selection answer names a part with no words, so it keeps the
+ * whole Message.
  */
 export function relayReplyQuote(facts, target) {
     if (!target || target.chat_id !== facts.chatId)
@@ -70,7 +72,7 @@ export function relayReplyQuote(facts, target) {
     const swiped = parts.length > 1 && facts.replyToPartIndex !== undefined
         ? parts[facts.replyToPartIndex]
         : undefined;
-    const body = renderRelayMessageParts(swiped ? [swiped] : parts);
+    const body = renderRelayMessageParts(swiped && swiped.type !== "buttons" && swiped.type !== "selection" ? [swiped] : parts);
     const sender = target.from_handle?.display_name?.trim()
         || target.from_handle?.handle
         || target.from
@@ -82,6 +84,16 @@ export function relayReplyQuote(facts, target) {
         senderAllowed: true,
     };
 }
+/**
+ * Whether the part a reply names may itself be replied to. A tap names the
+ * agent's buttons part and a selection answer its selection part; no reply may
+ * point at those (Relay v1 ReplyTo.part_index), so a person's tap keeps its
+ * own Message as the reply target.
+ */
+function repliable(target, partIndex) {
+    const part = target?.parts?.[partIndex ?? 0];
+    return part !== undefined && part.type !== "buttons" && part.type !== "selection";
+}
 /**
  * The answer to another agent names the Message it answers: the model's own
  * reply target when it chose one, else the agent's Message. Where no reply may
@@ -202,18 +214,23 @@ export async function dispatchRelayEvent(params) {
         params.warn?.(`relay: Contact @${facts.handle} did not pass OpenClaw ingress (${access.ingress.decision}:${access.ingress.reasonCode})`);
         return;
     }
-    // An agent's reply target is only its own Message (agentReplyLink); a
-    // person's is the Message they replied from, as before.
+    // An agent's reply target is only its own Message (agentReplyLink). A
+    // person's is the Message they replied to, OpenClaw's ReplyToId, as its
+    // Telegram channel sets `reply.replyToId` to Telegram's reply_to_message:
+    // the prompt names it beside the quote. A tap or a selection answer names a
+    // part no reply may target, so it keeps the person's own Message.
+    const quote = relayReplyQuote(facts, repliedTo);
     const replyTarget = facts.fromAgent
         ? facts.agentReplyLink
-        : facts.replyAnchorId ?? facts.replyToId;
+        : quote && repliable(repliedTo, facts.replyToPartIndex)
+            ? quote.id
+            : facts.replyAnchorId ?? facts.replyToId;
     const body = buildEnvelope({
         channel: "Relay",
         from: `${facts.displayName} (@${facts.handle})`,
         ...(facts.timestamp ? { timestamp: facts.timestamp } : {}),
         body: facts.text,
     });
-    const quote = relayReplyQuote(facts, repliedTo);
     const ctxPayload = buildChannelInboundEventContext({
         channel: "relay",
         accountId: route.accountId ?? params.account.accountId,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@relaymessenger/openclaw-plugin",
-  "version": "0.4.7-staging.40",
+  "version": "0.4.7-staging.41",
   "description": "Native Relay channel plugin for OpenClaw",
   "license": "MIT",
   "type": "module",
@@ -37,7 +37,7 @@
     "prepack": "npm run build"
   },
   "dependencies": {
-    "@relaymessenger/sdk": "0.3.6-staging.47"
+    "@relaymessenger/sdk": "0.3.6-staging.48"
   },
   "devDependencies": {
     "@types/node": "^26.6.2",

package/src/dispatch.ts

@@ -114,8 +114,10 @@ async function readReplyTarget(params: {
  * OpenClaw's own reply context, `supplemental.quote`, which it renders to the
  * model as "Reply target of current user message" (id, sender, body), as its
  * Telegram channel fills it from Telegram's `reply_to_message`. A reply names
- * one bubble: when the target has more than one part, only the swiped part is
- * quoted, the rule Relay's iOS app uses to draw the quote.
+ * one bubble: a multipart target is narrowed to the swiped part, the rule
+ * Relay's iOS app uses to draw the quote (the SDK's `replyTargetParts`); a
+ * tap or a selection answer names a part with no words, so it keeps the
+ * whole Message.
  */
 export function relayReplyQuote(
   facts: Pick<RelayInboundFacts, "chatId" | "replyToPartIndex">,
@@ -126,7 +128,9 @@ export function relayReplyQuote(
   const swiped = parts.length > 1 && facts.replyToPartIndex !== undefined
     ? parts[facts.replyToPartIndex]
     : undefined;
-  const body = renderRelayMessageParts(swiped ? [swiped] : parts);
+  const body = renderRelayMessageParts(
+    swiped && swiped.type !== "buttons" && swiped.type !== "selection" ? [swiped] : parts,
+  );
   const sender = target.from_handle?.display_name?.trim()
     || target.from_handle?.handle
     || target.from
@@ -139,6 +143,17 @@ export function relayReplyQuote(
   };
 }
 
+/**
+ * Whether the part a reply names may itself be replied to. A tap names the
+ * agent's buttons part and a selection answer its selection part; no reply may
+ * point at those (Relay v1 ReplyTo.part_index), so a person's tap keeps its
+ * own Message as the reply target.
+ */
+function repliable(target: Message | undefined, partIndex: number | undefined): boolean {
+  const part = target?.parts?.[partIndex ?? 0];
+  return part !== undefined && part.type !== "buttons" && part.type !== "selection";
+}
+
 /**
  * The answer to another agent names the Message it answers: the model's own
  * reply target when it chose one, else the agent's Message. Where no reply may
@@ -281,18 +296,23 @@ export async function dispatchRelayEvent(params: {
     return;
   }
 
-  // An agent's reply target is only its own Message (agentReplyLink); a
-  // person's is the Message they replied from, as before.
+  // An agent's reply target is only its own Message (agentReplyLink). A
+  // person's is the Message they replied to, OpenClaw's ReplyToId, as its
+  // Telegram channel sets `reply.replyToId` to Telegram's reply_to_message:
+  // the prompt names it beside the quote. A tap or a selection answer names a
+  // part no reply may target, so it keeps the person's own Message.
+  const quote = relayReplyQuote(facts, repliedTo);
   const replyTarget = facts.fromAgent
     ? facts.agentReplyLink
-    : facts.replyAnchorId ?? facts.replyToId;
+    : quote && repliable(repliedTo, facts.replyToPartIndex)
+      ? quote.id
+      : facts.replyAnchorId ?? facts.replyToId;
   const body = buildEnvelope({
     channel: "Relay",
     from: `${facts.displayName} (@${facts.handle})`,
     ...(facts.timestamp ? { timestamp: facts.timestamp } : {}),
     body: facts.text,
   });
-  const quote = relayReplyQuote(facts, repliedTo);
   const ctxPayload = buildChannelInboundEventContext({
     channel: "relay",
     accountId: route.accountId ?? params.account.accountId,