@agentchatme/openclaw 0.6.20 → 0.7.2

package/dist/index.js

@@ -1854,7 +1854,7 @@ var CircuitBreaker = class {
 };
 
 // src/version.ts
-var PACKAGE_VERSION = "0.6.20";
+var PACKAGE_VERSION = "0.7.2";
 
 // src/outbound.ts
 var DEFAULT_RETRY_POLICY = {
@@ -3233,6 +3233,71 @@ var ACCOUNT_PARAM = Type.Optional(
 );
 var agentchatAgentToolsFactory = ({ cfg }) => {
   const tools = [
+    // ─── Cross-channel send ──────────────────────────────────────────────
+    //
+    // OpenClaw's core `message` tool is the conventional sender — and is
+    // the right pick when the current turn was triggered by an AgentChat
+    // inbound. But when the inbound arrived on a different channel
+    // (Telegram, Slack, Discord, the OpenClaw CLI), the per-turn `message`
+    // tool's `fallbackChannel` is bound to that channel, so an implicit
+    // `message({to, text})` call from the model fall-back-routes to the
+    // wrong outbound and gets rejected by that channel's target
+    // normalization. The model paraphrases the rejection back to the
+    // operator as "Telegram is not letting me…".
+    //
+    // This tool sidesteps the binding entirely. ChannelAgentTools are not
+    // gated by `currentChannelProvider`, so this is visible and invokable
+    // on every turn regardless of inbound source. The execute path runs
+    // through our cached SDK client against the AgentChat REST API — no
+    // OpenClaw channel routing in scope, no implicit fallback, no
+    // requireExplicitMessageTarget gate. Reach for this whenever the
+    // operator says "message X on AgentChat" or the model otherwise needs
+    // a deterministic, channel-agnostic AgentChat send.
+    tool({
+      name: "agentchat_send_message",
+      description: "Send a peer-to-peer message on AgentChat to another agent by handle. Use this whenever the operator asks you to message someone on AgentChat, regardless of which channel the request arrived on (Telegram, Slack, the OpenClaw CLI, AgentChat itself \u2014 anywhere). This is the right tool for cross-channel sends because it is not bound to the inbound channel; the shared `message` tool defaults its destination to the inbound channel and will route incorrectly when the operator asks you to send on AgentChat from a different channel's turn. Returns the new message id once delivered.",
+      parameters: Type.Object({
+        handle: Type.String({
+          minLength: 3,
+          maxLength: 31,
+          description: "The recipient agent's handle, with or without the leading @. Lowercase letters, digits, and hyphens; must start with a letter; 3-30 chars after stripping the @."
+        }),
+        message: Type.String({
+          minLength: 1,
+          maxLength: 8e3,
+          description: "The message text to send. Plain text \u2014 the platform is a transport, not a renderer."
+        }),
+        replyToMessageId: Type.Optional(
+          Type.String({
+            description: "Optional id of an existing message you are replying to. Threads the response so the recipient's client can render it as a reply."
+          })
+        ),
+        account: ACCOUNT_PARAM
+      }),
+      execute: async (_id, p) => {
+        const r = clientFor(cfg, p.account);
+        if ("error" in r) return err2(r.error);
+        const handle = stripAt(p.handle);
+        try {
+          const result = await r.client.sendMessage({
+            to: handle,
+            content: { text: p.message },
+            ...p.replyToMessageId ? { metadata: { reply_to: p.replyToMessageId } } : {}
+          });
+          const summaryParts = [
+            `sent to @${handle} \u2014 message ${result.message.id} in ${result.message.conversation_id}`
+          ];
+          if (result.backlogWarning) {
+            summaryParts.push(
+              `\u26A0 recipient backlog at ${result.backlogWarning.undeliveredCount} undelivered \u2014 consider slowing follow-ups`
+            );
+          }
+          return ok2(summaryParts.join("\n"));
+        } catch (e) {
+          return err2(toMsg(e));
+        }
+      }
+    }),
     // ─── Contacts ─────────────────────────────────────────────────────────
     tool({
       name: "agentchat_add_contact",