@clawling/clawchat-plugin-openclaw 2026.9.13-2 → 2026.9.13-3

package/dist/index.js

@@ -5,7 +5,7 @@ import { openclawClawlingConfigSchema } from "./src/config.js";
 import { registerClawChatPromptInjection, } from "./src/prompt-injection.js";
 import { setOpenclawClawlingRuntime } from "./src/runtime.js";
 import { registerOpenclawClawlingTools } from "./src/tools.js";
-export default defineChannelPluginEntry({
+const channelEntry = defineChannelPluginEntry({
     id: "clawchat-plugin-openclaw",
     name: "Clawling Chat",
     description: "Clawling Chat Protocol v2 channel plugin",
@@ -13,7 +13,6 @@ export default defineChannelPluginEntry({
     configSchema: { schema: openclawClawlingConfigSchema },
     setRuntime: setOpenclawClawlingRuntime,
     registerFull(api) {
-        registerOpenclawClawlingCommands(api);
         registerClawChatPromptInjection(api);
         registerOpenclawClawlingTools(api);
         // NOTE: the legacy-rename config migration is intentionally NOT registered
@@ -25,3 +24,29 @@ export default defineChannelPluginEntry({
         // migration is wired into setup-entry.ts instead.
     },
 });
+/**
+ * Chat slash commands (`/clawchat-activate`, `/clawchat-output`) are registered
+ * in EVERY registration mode except `cli-metadata`, not inside `registerFull`.
+ *
+ * The host loads the plugin more than once per process — a `full` load and,
+ * on 2026.8+ hosts, a `discovery` load bound to the gateway request scope —
+ * and it matches chat slash commands against THAT discovery registry
+ * (`resolveSelectedPluginCommandRegistry` prefers the request-scoped one).
+ * `defineChannelPluginEntry` only runs `registerFull` for `full` /
+ * `tool-discovery`, so commands registered there never reach the registry the
+ * chat path consults: the message fell through to the LLM as ordinary text.
+ * The pinned floor host has no `registerCapabilities` hook, so wrap `register`
+ * instead. Each load registers the commands once; a duplicate registration
+ * would mark the plugin as errored on the host side.
+ */
+export default {
+    // Newer hosts expose `configSchema` as a lazy getter; the spread evaluates it
+    // once here, which is fine because the schema is a static object.
+    ...channelEntry,
+    register: (api) => {
+        channelEntry.register(api);
+        if (api.registrationMode !== "cli-metadata") {
+            registerOpenclawClawlingCommands(api);
+        }
+    },
+};

package/index.ts

@@ -1,4 +1,5 @@
 import { defineChannelPluginEntry } from "openclaw/plugin-sdk/channel-core";
+import type { OpenClawPluginApi } from "openclaw/plugin-sdk";
 import { openclawClawlingPlugin } from "./src/channel.ts";
 import { registerOpenclawClawlingCommands } from "./src/commands.ts";
 import { openclawClawlingConfigSchema } from "./src/config.ts";
@@ -9,7 +10,7 @@ import {
 import { setOpenclawClawlingRuntime } from "./src/runtime.ts";
 import { registerOpenclawClawlingTools } from "./src/tools.ts";
 
-export default defineChannelPluginEntry({
+const channelEntry = defineChannelPluginEntry({
   id: "clawchat-plugin-openclaw",
   name: "Clawling Chat",
   description: "Clawling Chat Protocol v2 channel plugin",
@@ -17,7 +18,6 @@ export default defineChannelPluginEntry({
   configSchema: { schema: openclawClawlingConfigSchema },
   setRuntime: setOpenclawClawlingRuntime,
   registerFull(api) {
-    registerOpenclawClawlingCommands(api);
     registerClawChatPromptInjection(api as unknown as ClawChatPromptInjectionApi);
     registerOpenclawClawlingTools(api);
     // NOTE: the legacy-rename config migration is intentionally NOT registered
@@ -29,3 +29,30 @@ export default defineChannelPluginEntry({
     // migration is wired into setup-entry.ts instead.
   },
 });
+
+/**
+ * Chat slash commands (`/clawchat-activate`, `/clawchat-output`) are registered
+ * in EVERY registration mode except `cli-metadata`, not inside `registerFull`.
+ *
+ * The host loads the plugin more than once per process — a `full` load and,
+ * on 2026.8+ hosts, a `discovery` load bound to the gateway request scope —
+ * and it matches chat slash commands against THAT discovery registry
+ * (`resolveSelectedPluginCommandRegistry` prefers the request-scoped one).
+ * `defineChannelPluginEntry` only runs `registerFull` for `full` /
+ * `tool-discovery`, so commands registered there never reach the registry the
+ * chat path consults: the message fell through to the LLM as ordinary text.
+ * The pinned floor host has no `registerCapabilities` hook, so wrap `register`
+ * instead. Each load registers the commands once; a duplicate registration
+ * would mark the plugin as errored on the host side.
+ */
+export default {
+  // Newer hosts expose `configSchema` as a lazy getter; the spread evaluates it
+  // once here, which is fine because the schema is a static object.
+  ...channelEntry,
+  register: (api: OpenClawPluginApi) => {
+    channelEntry.register(api);
+    if (api.registrationMode !== "cli-metadata") {
+      registerOpenclawClawlingCommands(api);
+    }
+  },
+};

package/package.json

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