@clawling/clawchat-plugin-openclaw 2026.8.5-2 → 2026.8.6-1

package/dist/src/inbound.js

@@ -1,4 +1,4 @@
-import { EVENT, } from "./protocol-types.js";
+import { EVENT, MENTION_ALL_USER_ID, } from "./protocol-types.js";
 import { extractMediaFragments, fragmentsToText } from "./message-mapper.js";
 import { hasRenderableText, isInboundMessagePayload } from "./protocol.js";
 function normalizeSender(sender) {
@@ -73,11 +73,16 @@ function mentionedUserIds(mentions) {
 /**
  * Exported for direct unit testing. Direct chats always count as addressed;
  * group chats require a mention unless config opts into all group messages.
+ *
+ * `MENTION_ALL_USER_ID` ("all") is the `@everyone` sentinel — it addresses
+ * every member of the room, this agent included, so it counts as a mention
+ * even though it never equals our own user id.
  */
 export function detectMention(params) {
     if (params.chatType === "direct")
         return true;
-    return mentionedUserIds(normalizeMentionUsers(params.mentions)).includes(params.userId);
+    const ids = mentionedUserIds(normalizeMentionUsers(params.mentions));
+    return ids.includes(params.userId) || ids.includes(MENTION_ALL_USER_ID);
 }
 export async function dispatchOpenclawClawlingInbound(params) {
     const { envelope, account, log } = params;

package/dist/src/protocol-types.js

@@ -22,6 +22,14 @@ export const EVENT = {
     PING: "ping",
     PONG: "pong",
 };
+/**
+ * The `user_id` an `@everyone` mention carries on the wire — a reserved
+ * sentinel, not a real user id. The server never expands it into one mention
+ * per member, so every reader must decide for itself that it includes them.
+ * It can appear both as a `mention` fragment and as a `context.mentions`
+ * element. See `docs/client-integration.md` §10.2.
+ */
+export const MENTION_ALL_USER_ID = "all";
 export class AuthError extends Error {
     name = "AuthError";
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clawling/clawchat-plugin-openclaw",
-  "version": "2026.8.5-2",
+  "version": "2026.8.6-1",
   "description": "OpenClaw ClawChat channel plugin",
   "license": "MIT",
   "author": "CLAWLING PTE. LTD.",

package/src/inbound.ts

@@ -1,5 +1,6 @@
 import {
   EVENT,
+  MENTION_ALL_USER_ID,
   type ChatType,
   type Envelope,
 } from "./protocol-types.ts";
@@ -180,6 +181,10 @@ function mentionedUserIds(mentions: MentionedUser[]): string[] {
 /**
  * Exported for direct unit testing. Direct chats always count as addressed;
  * group chats require a mention unless config opts into all group messages.
+ *
+ * `MENTION_ALL_USER_ID` ("all") is the `@everyone` sentinel — it addresses
+ * every member of the room, this agent included, so it counts as a mention
+ * even though it never equals our own user id.
  */
 export function detectMention(params: {
   mentions: unknown[];
@@ -187,7 +192,8 @@ export function detectMention(params: {
   userId: string;
 }): boolean {
   if (params.chatType === "direct") return true;
-  return mentionedUserIds(normalizeMentionUsers(params.mentions)).includes(params.userId);
+  const ids = mentionedUserIds(normalizeMentionUsers(params.mentions));
+  return ids.includes(params.userId) || ids.includes(MENTION_ALL_USER_ID);
 }
 
 export async function dispatchOpenclawClawlingInbound(

package/src/protocol-types.ts

@@ -23,6 +23,15 @@ export const EVENT = {
   PONG: "pong",
 } as const;
 
+/**
+ * The `user_id` an `@everyone` mention carries on the wire — a reserved
+ * sentinel, not a real user id. The server never expands it into one mention
+ * per member, so every reader must decide for itself that it includes them.
+ * It can appear both as a `mention` fragment and as a `context.mentions`
+ * element. See `docs/client-integration.md` §10.2.
+ */
+export const MENTION_ALL_USER_ID = "all";
+
 export type KnownEventName = typeof EVENT[keyof typeof EVENT];
 export type EventName = KnownEventName | string;
 export type ChatType = "direct" | "group";