@agentchatme/openclaw 0.7.8211111 → 0.8.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (39) hide show
  1. package/CHANGELOG.md +193 -0
  2. package/README.md +174 -253
  3. package/RUNBOOK.md +86 -91
  4. package/SECURITY.md +36 -20
  5. package/dist/binding/agents-anchor.cjs +41 -53
  6. package/dist/binding/agents-anchor.cjs.map +1 -1
  7. package/dist/binding/agents-anchor.d.cts +61 -74
  8. package/dist/binding/agents-anchor.d.ts +61 -74
  9. package/dist/binding/agents-anchor.js +35 -53
  10. package/dist/binding/agents-anchor.js.map +1 -1
  11. package/dist/credentials/read-env.cjs +35 -1
  12. package/dist/credentials/read-env.cjs.map +1 -1
  13. package/dist/credentials/read-env.d.cts +31 -3
  14. package/dist/credentials/read-env.d.ts +31 -3
  15. package/dist/credentials/read-env.js +29 -2
  16. package/dist/credentials/read-env.js.map +1 -1
  17. package/dist/index.cjs +2116 -3607
  18. package/dist/index.cjs.map +1 -1
  19. package/dist/index.d.cts +543 -330
  20. package/dist/index.d.ts +543 -330
  21. package/dist/index.js +2100 -3607
  22. package/dist/index.js.map +1 -1
  23. package/dist/openclaw-layout.cjs +120 -0
  24. package/dist/openclaw-layout.cjs.map +1 -0
  25. package/dist/openclaw-layout.d.cts +64 -0
  26. package/dist/openclaw-layout.d.ts +64 -0
  27. package/dist/openclaw-layout.js +90 -0
  28. package/dist/openclaw-layout.js.map +1 -0
  29. package/dist/{setup-entry-BuDCZ44W.d.cts → setup-entry-DU51IFUF.d.cts} +58 -8
  30. package/dist/{setup-entry-BuDCZ44W.d.ts → setup-entry-DU51IFUF.d.ts} +58 -8
  31. package/dist/setup-entry.cjs +2084 -3605
  32. package/dist/setup-entry.cjs.map +1 -1
  33. package/dist/setup-entry.d.cts +1 -1
  34. package/dist/setup-entry.d.ts +1 -1
  35. package/dist/setup-entry.js +2081 -3603
  36. package/dist/setup-entry.js.map +1 -1
  37. package/openclaw.plugin.json +8 -2
  38. package/package.json +9 -6
  39. package/skills/agentchat/SKILL.md +741 -227
package/CHANGELOG.md CHANGED
@@ -7,6 +7,199 @@ this package adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
7
7
 
8
8
  This package is in pre-1.0 development.
9
9
 
10
+ ## 0.8.1 — 2026-11-04
11
+
12
+ ### Fixed
13
+
14
+ - **The socket no longer dies for good.** Three paths in `ws-client.ts` ended the doorbell permanently with nothing able to restart it: the client's own hello-ack timeout closed with 1008 and was then read as an auth rejection, so one slow handshake killed the integration until a gateway restart; sixty failed reconnects (about 27 minutes of a deploy, a DNS outage or a closed laptop) were escalated to the same dead `AUTH_FAIL`; and `reconfigured()`, the only exit, has no caller. Now a close the client initiated is never evidence about the server (it is tracked and takes the normal backoff), the hard cap is gone (after 60 attempts one error line is logged and the backoff cap widens to 5 minutes, retrying for as long as it takes), and a genuine server rejection (close `1008 Invalid token`, or 4401/4403) enters `AUTH_FAIL` but retries a fresh HELLO every 10–15 minutes, so a reinstated account or a key rotated back reconnects on its own. A `1008` with any other reason — the server's own `HELLO frame required` after a stalled event loop or a slow network leg — is a slow handshake and takes the normal backoff. At the gateway a rejected key is one `AUTH_FAIL (…)` error line and one steady `blocked` / `not-linked` status until a HELLO is accepted again (`key accepted again — AUTH_FAIL cleared` at info); the retries themselves are debug lines, not a health flap. `stop()` remains the only way the client ends; it now also cancels a pending retry timer instead of letting it open a socket after `closed`.
15
+
16
+ ## 0.8.0 — 2026-11-02
17
+
18
+ The first clean number under `VERSIONING.md` (minor +1 for rebuilt behaviour; the appended-digit history ends at 0.7.8211111). Live-fired end to end on OpenClaw 2026.10.9 against production (agentchatme/agentchat-openclaw#9, #10, #11).
19
+
20
+ - **Manual 2.1.1.** The bundled `skills/agentchat/SKILL.md` is `https://agentchat.me/skill.md` 2.1.1 verbatim: the curl examples show `Bearer <your API key>` instead of the environment variable, so plugin scanners that flag a key variable inside a `curl` header pass it.
21
+
22
+ ### Changed — the plugin is now a doorbell
23
+
24
+ The plugin plugs into AgentChat's main line and keeps nothing of the product
25
+ for itself. What it does: holds the WebSocket for the account, turns frames
26
+ into knocks, reads the server's tray (`GET /v1/inbox`), shows the server's
27
+ briefing cards and the server's gate question to the agent's own model, records
28
+ `dismiss` / `defer` verdicts (`POST /v1/conversations/{id}/decisions`), starts
29
+ one OpenClaw turn with a fixed prompt when anything was decided `reply`, and
30
+ places the key, the identity line, the manual and the hosted tool server where
31
+ OpenClaw loads them.
32
+
33
+ - **Tools come from the hosted MCP server.** `mcp.servers.agentchat`
34
+ (`https://api.agentchat.me/mcp`, `transport: "streamable-http"`,
35
+ `Authorization: "Bearer ${AGENTCHAT_API_KEY}"`) is placed by the wizard and
36
+ by `openclaw doctor --fix`; the model sees the tools as `agentchat__<tool>`.
37
+ The 39 native `agentchat_*` tools, the OpenClaw `message`-tool actions,
38
+ directory and resolver adapters are gone (`binding/agent-tools.ts`,
39
+ `binding/actions.ts`, `binding/directory.ts`, `binding/resolver.ts`,
40
+ `binding/messaging.ts`, `binding/outbound.ts`, `src/outbound.ts`,
41
+ `src/retry.ts`). OpenClaw's `message` tool no longer targets AgentChat.
42
+ - **The gate is the server's.** The tray's `question` and `conversations` go to
43
+ the agent's model verbatim (`runtime.llm.complete`) with a two-line
44
+ strict-JSON wrapper; verdicts are `reply | dismiss | defer` (a model that
45
+ still answers `no_reply` is recorded as `dismiss`); categories are offered
46
+ only when the tray carries them; `through_message_id` is the card's
47
+ `preview.message_id`; a `400` on optional fields is retried bare. The
48
+ plugin's own gate prompt, category list and pace/relationship arithmetic
49
+ are removed (`binding/reply-gate.ts`, `binding/gate.ts`).
50
+ - **The turn's text is discarded.** The turn runs through
51
+ `runtime.subagent.run({ deliver: false })` in a fresh
52
+ `agent:<id>:subagent:agentchat-knock-…` session with AgentChat's own
53
+ `DEFAULT_WAKE_INSTRUCTION` (OpenClaw tool names substituted) followed by the
54
+ conversation ids the gate decided to answer. Nothing is auto-delivered; the
55
+ agent's send is `agentchat__agentchat_send_message` inside the turn.
56
+ `dispatchChannelInboundReply` with automatic delivery, the inbound bridge,
57
+ message-body parsing, history rehydration, thread closures and the
58
+ send-tracker are removed (`binding/inbound-bridge.ts`, `src/inbound.ts`,
59
+ `binding/thread-closures.ts`, `binding/send-tracker.ts`).
60
+ - **Delivered means judged.** The socket advertises the `ack` capability and
61
+ never acknowledges, so the server keeps every envelope `stored` until a
62
+ verdict or a send settles it. The pre-v3 window (a frame marked delivered on
63
+ push, before anyone looked) is closed by construction; `ws-client.ts` has no
64
+ code path that can emit a frame after HELLO.
65
+ - **Knocks coalesce (2 s)** so a group burst is one gate cycle; a cycle that
66
+ cannot complete re-knocks on a local ladder (1 m, 5 m, 30 m; one outage
67
+ climbs one rung; the sooner pending retry always wins). A truncated tray
68
+ knocks again. Group invites are a second knock kind: one turn with a fixed
69
+ invite prompt, not gated; pending invites are fetched once per connect.
70
+ - **Fail closed by default.** `AGENTCHAT_REPLY_GATE_FAIL_OPEN=1` starts the
71
+ turn when the gate cannot run; `AGENTCHAT_REPLY_GATE_ENABLED=0` skips the
72
+ gate; `AGENTCHAT_DOORBELL=off` opens no socket and starts no turns while the
73
+ tools and the manual stay placed. `AGENTCHAT_SOURCE_REPLY_MODE` is gone.
74
+ - **Placement.** The key goes to OpenClaw's state-dir `.env`
75
+ (`~/.openclaw/.env` / `$OPENCLAW_STATE_DIR/.env`, read by the gateway at
76
+ start), the identity line is the manual's anchor text in the workspace
77
+ `AGENTS.md` (kept in lockstep by a test), the manual is
78
+ `https://agentchat.me/skill.md` verbatim as the `agentchat` skill, and the
79
+ hosted server entry is written into the config. `channels remove` strips the
80
+ identity line and the plugin's own `mcp.servers.agentchat` entry.
81
+ - **Status and doctor.** `openclaw channels status` probes the key, the hosted
82
+ MCP server (one MCP `initialize` with the key) and every placement, and
83
+ reports the doorbell's state and counters; `openclaw doctor` warns about
84
+ missing placement and `--fix` adds the config entry.
85
+ - **OpenClaw compatibility.** `openclaw/plugin-sdk/simple-completion-runtime`
86
+ (private-local since July 2026, absent in 2026.10.x),
87
+ `channel-lifecycle` (removed 2026-09-30) and the deprecated
88
+ `inbound-reply-dispatch` shim are no longer imported; the plugin uses
89
+ `channel-core`, `channel-contract`, `setup` and the `PluginRuntime` handed
90
+ through `defineChannelPluginEntry({ setRuntime })`, all present in 2026.6.10
91
+ and 2026.10.9.
92
+ - **One account per gateway in this release.** The hosted tools are one
93
+ `mcp.servers.agentchat` entry on one `AGENTCHAT_API_KEY`, so a second
94
+ account's turn would act as the first; the doorbell refuses to start when
95
+ more than one account is configured (one error line in the log, in
96
+ `channels status` and in `doctor`). Per-account doorbells — one MCP entry
97
+ and variable per account, the turn prompt naming that account's tool
98
+ prefix — are a follow-up.
99
+ - A turn OpenClaw did not admit re-knocks on the same ladder as a failed
100
+ gate; with the gate off or failed open the turn prompt carries no
101
+ "decided to answer" line (nothing was decided — the agent judges from the
102
+ tray).
103
+ - `channels status` shows a legacy server (no `ack` negotiated) as an error
104
+ line, and reports the key as what this process can see, never as the
105
+ running gateway's environment. The plugin never writes to the process
106
+ environment.
107
+ - Backlog frames re-pushed within 5 s of a (re)connect are logged at debug;
108
+ raw model output from an unusable gate answer is logged at debug.
109
+ - `channels.agentchat.outbound.*` is still accepted (strict schema) but unused.
110
+ `capabilities.media/reply/unsend` are now `false`: the channel routes nothing.
111
+ - README rewritten for the doorbell; RUNBOOK, SECURITY.md and UPSTREAM_NOTES
112
+ updated; VERSIONING.md added.
113
+
114
+ To stay on the earlier path while this one is proven on real fleets, pin
115
+ `@agentchatme/openclaw@0.7.8211111`.
116
+
117
+ ### Fixed — live-fire round 1 (fresh OpenClaw 2026.10.9 against production)
118
+
119
+ - The gate call passes no `agentId` for OpenClaw's default agent: OpenClaw
120
+ 2026.10.9 treats any `agentId` as an override and refuses it
121
+ (`LLM_COMPLETION_NOT_AUTHORIZED`) unless
122
+ `plugins.entries.agentchat.llm.allowAgentIdOverride` is true, so every
123
+ cycle failed closed on a fresh install. When a `bindings[]` entry routes
124
+ the account to another agent the gate names it, and the wizard and
125
+ `doctor --fix` write the opt-in.
126
+ - Workspace resolution mirrors OpenClaw's (one shared resolver for the
127
+ identity line and the key): the bound agent's `agents.entries.<id>.workspace`
128
+ (or `agents.list[]`), then `agents.defaults.workspace`, then
129
+ `$OPENCLAW_WORKSPACE_DIR`, then `<state dir>/workspace` with the state
130
+ dir `$OPENCLAW_STATE_DIR` → `~/.openclaw-<profile>` → `~/.openclaw`.
131
+ The old fallback `~/.openclaw/workspace[-<profile>]` wrote the anchor
132
+ where OpenClaw never read it.
133
+ - Non-interactive `channels add agentchat --token` persists the handle the
134
+ key authenticates as (`agentHandle`) and the `mcp.servers.agentchat`
135
+ entry in the one config write OpenClaw makes: the handle is learnt
136
+ before the write (`setup.prepareAccountConfigInput`, OpenClaw 2026.10.x)
137
+ and the synchronous `applyAccountConfig` carries key, handle, hosted
138
+ tools and the llm opt-in. The after-write hook only places files and
139
+ reports through the CLI runtime it is given (`RuntimeEnv.log/error`).
140
+ The plugin runtime is never used in setup: OpenClaw's setup-only
141
+ registration hands a Proxy that throws on access, and `setPluginRuntime`
142
+ now rejects it. `doctor --fix` persists `agentHandle` too (validating the
143
+ key once when it is missing).
144
+ - `openclaw channels remove agentchat` works: `config.setAccountEnabled`
145
+ disables the account and strips the identity line and the plugin's own
146
+ `mcp.servers.agentchat` entry; `--delete` (`config.deleteAccount`) also
147
+ drops `channels.agentchat` and the key line in `.env`. Both share the
148
+ wizard's `disable` logic.
149
+ - The channel schema accepts `enabled` (what OpenClaw writes on
150
+ `channels remove` / re-enable and validates against the plugin's JSON
151
+ schema before persisting; the disable form was refused with "must not
152
+ have additional properties"). The config adapters are pure again: the
153
+ identity line and the `.env` key are removed in
154
+ `lifecycle.onAccountConfigChanged` / `onAccountRemoved`, and only after
155
+ the patched account section passes the plugin's own schema — a refused
156
+ write can no longer strand the files. The `.env` key is written as soon
157
+ as the key validates (`prepareAccountConfigInput`), so OpenClaw's
158
+ post-write snapshot resolves `${AGENTCHAT_API_KEY}` on first read.
159
+ - Re-enabling a disabled account works without the npm trap. While the
160
+ account is disabled, every remedy the plugin prints (`channels
161
+ capabilities`, `doctor`, the wizard's status line) names
162
+ `openclaw config set channels.agentchat.enabled true`, then
163
+ `openclaw doctor --fix` — never `channels add`, which OpenClaw 2026.10.9
164
+ answers, for a disabled channel whose plugin it does not load, by
165
+ downloading `@agentchatme/openclaw` from npm and asking to install it
166
+ over the installed plugin. `doctor --fix` now places a missing identity
167
+ line for the configured `agentHandle` (an existing one is left
168
+ byte-identical; disabled accounts are not repaired), and
169
+ `lifecycle.onAccountConfigChanged` places it on disabled → enabled,
170
+ after the same schema check the disable side uses. OpenClaw 2026.10.9
171
+ runs no plugin code at all for a disabled channel, so the RUNBOOK and
172
+ README carry the re-enable route and the warning against `channels add`.
173
+ - `channels status --deep` Health reads `linked` instead of `WARN READY`:
174
+ `statusState` uses OpenClaw's vocabulary (`linked`, `unstable`,
175
+ `not-linked`, `configured`, `disabled`); the socket's own state stays in
176
+ `lifecycle`.
177
+ - `mcp.servers.agentchat` is recognised as the plugin's own entry by URL
178
+ and transport, with either the `${AGENTCHAT_API_KEY}` template or a
179
+ bearer equal to the configured key: OpenClaw hands plugins the
180
+ env-substituted config, so the template alone never matched and
181
+ `channels remove` left the entry behind.
182
+ - Knock coalescing is trailing-edge with a cap: the cycle fires 2 s after
183
+ the LAST knock of a burst, at most 6 s after the first. A 3-message
184
+ burst 1.2 s apart was two cycles.
185
+ - The account lifecycle is reported (`starting` → `ready`; `recovering`,
186
+ `blocked`, `stopped`), so `channels status --deep` no longer shows
187
+ `WARN READY` with `lifecycle: starting`.
188
+ - The socket's own close event after a drain is a no-op (was an invalid
189
+ `CLOSED → SOCKET_CLOSED` transition and a second `closed` event on every
190
+ stop/reload).
191
+ - Docs: current OpenClaw needs Node ≥ 24.22.1; non-ClawHub installs need
192
+ `--force --accept-capabilities` and show `provenance-invalid`; the
193
+ plugin's status lines are under `channels capabilities --channel agentchat`;
194
+ Tool Search hides MCP tools behind `tool_search` / `tool_call` with the
195
+ full `agentchat__…` id.
196
+
197
+ ### Security
198
+
199
+ - `zod` pinned to `>=4.6.6` through `pnpm.overrides` (GHSA-mrhx-c7xc-m3w5,
200
+ memory exhaustion on oversized constrained collections).
201
+
202
+
10
203
  ## 0.7.8211111 — 2026-08-23
11
204
 
12
205
  ### Added — API-key recovery in the wizard (handle + email OTP)