@agentchatme/openclaw 0.6.17 → 0.6.18

package/dist/setup-entry.js

@@ -817,19 +817,16 @@ var agentchatSetupWizard = {
   },
   completionNote: {
     title: "AgentChat is ready",
-    lines: [
-      // Why this line exists: after our wizard returns, OpenClaw's
-      // setupChannels loops back to "Select a channel" so the user can
-      // wire up additional channels in the same session. From the user's
-      // vantage point this looks like the wizard restarted; tell them
-      // the loop is intentional and how to exit.
-      'On the next prompt, choose "Finished" to exit \u2014 or pick another channel to keep configuring.',
-      "",
-      "Next steps:",
-      "  \u2022 Start OpenClaw \u2014 the AgentChat channel auto-connects via WebSocket.",
-      "  \u2022 DM another agent:  @<handle> <message>",
-      "  \u2022 Docs:              https://agentchat.me/docs"
-    ]
+    // After our wizard returns, OpenClaw's setupChannels keeps running
+    // its own outer flow (a Select-a-channel loop, then optional
+    // follow-up prompts for display names and channel→agent binding).
+    // None of that is suppressible from a channel plugin — there's no
+    // field on ChannelSetupWizard that hides those prompts. So this
+    // note keeps to the only thing the user actually needs to know:
+    // pick Finished. The earlier "or pick another channel" copy read
+    // as a vague alt-branch and produced the "did this break?"
+    // reaction; one direct sentence is the cure.
+    lines: ['On the next prompt, choose "Finished" to exit.']
   },
   // `disable` fires on `openclaw channels remove agentchat`. We strip
   // the persistent AGENTS.md anchor here so the agent stops being told
@@ -1849,7 +1846,7 @@ var CircuitBreaker = class {
 };
 
 // src/version.ts
-var PACKAGE_VERSION = "0.6.17";
+var PACKAGE_VERSION = "0.6.18";
 
 // src/outbound.ts
 var DEFAULT_RETRY_POLICY = {