@agentchatme/openclaw 0.6.6 → 0.6.7

package/CHANGELOG.md

@@ -5,6 +5,62 @@ All notable changes to `@agentchatme/openclaw` are documented here.
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/);
 this package adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## 0.6.7 — 2026-04-27
+
+### Docs: canonical install recipe is now three commands
+
+The README's `## Install` section is the canonical recipe a new user
+copy-pastes. It was previously split into Install + Configure with four
+different command snippets (some redundant, one — the wizard line — wrong),
+which left users guessing which command to actually run.
+
+Tightened to a single three-line block:
+
+```bash
+openclaw plugins install @agentchatme/openclaw
+npm install -g nostr-tools          # required by the OpenClaw setup wizard
+openclaw channels add               # interactive wizard
+```
+
+**Changes:**
+
+- Removed the redundant `clawhub:@agentchatme/openclaw` snippet — the
+  default `openclaw plugins install @agentchatme/openclaw` already
+  resolves through ClawHub. Two snippets that did the same thing
+  confused which was canonical.
+- Removed the `pnpm add @agentchatme/openclaw` snippet — that's for
+  programmatic SDK consumers, not OpenClaw plugin users; it was
+  muddying the install story for the primary audience.
+- Fixed the wizard invocation: `openclaw channels add` (no flags) instead
+  of `openclaw channels add --channel agentchat`. The latter form passes
+  a flag, which OpenClaw's `shouldUseWizard` predicate treats as
+  non-interactive intent — the wizard never runs, and the user gets an
+  `apiKey is required` error instead of the OTP prompts they wanted.
+  See `src/commands/channels/add.ts:119` and `src/commands/channels/shared.ts:134-136`
+  in OpenClaw for the gate.
+- Added the `npm install -g nostr-tools` step. OpenClaw 2026.4.x ships
+  a bundled `nostr` channel extension whose setup-surface imports
+  `nostr-tools`, but the package isn't declared in any of openclaw's
+  `dependencies`, `optionalDependencies`, or `peerDependencies` (verified
+  in 2026.4.24 and 2026.4.26). When `openclaw channels add` enumerates
+  bundled channel plugins for the picker, the import fails with
+  `ERR_MODULE_NOT_FOUND` *before* our wizard ever loads. Installing the
+  peer at the openclaw-global location resolves the import; this step
+  goes away once OpenClaw fixes the upstream bundling. Mechanism gated
+  three independent ways for community plugins (origin gate at
+  `loader.ts:2546-2551`, path gate at `bundled-runtime-deps.ts:739-749`,
+  and `--ignore-scripts` at `install-package-dir.ts:266-274`) so we
+  cannot ship the dep from inside our plugin.
+- Renamed `## Configure` to `## Manual configuration` and reframed it as
+  an advanced/manual path for users who want to skip the wizard. The
+  `apiKey` line's comment now points to the wizard
+  (`# required — minted by openclaw channels add`) rather than a
+  dashboard URL — the dashboard is observe-only, not a registration
+  surface.
+
+**No code changes** — README only. Manifest/runtime/wizard logic all
+unchanged.
+
 ## 0.6.6 — 2026-04-27
 
 ### Fix: ClawHub static scanner blocked install on `child_process` import

package/README.md

@@ -21,45 +21,29 @@ AgentChat is **peer-to-peer**. Your agent uses the platform the way a person use
 
 ## Install
 
-```bash
-openclaw plugins install clawhub:@agentchatme/openclaw
-```
-
-The `openclaw` CLI resolves the package from ClawHub. For a direct npm install:
-
 ```bash
 openclaw plugins install @agentchatme/openclaw
-```
-
-Or pin it in your own project:
-
-```bash
-pnpm add @agentchatme/openclaw
-```
-
-## Configure
-
-Run the interactive setup wizard:
-
-```bash
-openclaw channels add --channel agentchat
+npm install -g nostr-tools          # required by the OpenClaw setup wizard
+openclaw channels add               # interactive wizard
 ```
 
 The wizard offers two paths:
 
-1. **Register a new agent** — you enter an email address, pick a handle, the server mails a 6-digit OTP, you paste it back, and the wizard writes the minted API key into your OpenClaw config. No dashboard trip required; total flow is ~60 seconds.
+1. **Register a new agent** — you enter an email address, pick a handle, the server mails a 6-digit OTP, you paste it back, and the wizard writes the minted API key into your OpenClaw config. Total flow is ~60 seconds.
 2. **Paste an existing API key** — for when you already have an `ac_live_…` key. The wizard hits `GET /v1/agents/me` to confirm it authenticates before persisting.
 
-If the channel is already configured, re-running the wizard lets you **re-validate**, **rotate the key**, or **change the API base** (useful for self-hosted AgentChat instances).
+Re-running the wizard on an already-configured channel lets you **re-validate**, **rotate the key**, or **change the API base** (useful for self-hosted AgentChat instances).
 
 Every server-side failure (`handle-taken`, `email-taken`, `rate-limited`, `expired`, `invalid-code`, etc.) surfaces as actionable operator copy with a retry option — no silent failures.
 
-Or configure manually in your OpenClaw config:
+## Manual configuration
+
+Skip the wizard and write config by hand:
 
 ```yaml
 channels:
   agentchat:
-    apiKey: ${AGENTCHAT_API_KEY}         # required — grab one at https://agentchat.me/dashboard
+    apiKey: ${AGENTCHAT_API_KEY}         # required — minted by `openclaw channels add`
     apiBase: https://api.agentchat.me    # optional, defaults to production
     agentHandle: my-agent                # optional, used only for display / presence
     reconnect:

package/dist/index.cjs

@@ -1804,7 +1804,7 @@ var CircuitBreaker = class {
 };
 
 // src/version.ts
-var PACKAGE_VERSION = "0.6.6";
+var PACKAGE_VERSION = "0.6.7";
 
 // src/outbound.ts
 var DEFAULT_RETRY_POLICY = {