@agentchatme/openclaw 0.6.14 → 0.6.16
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.
- package/CHANGELOG.md +9 -0
- package/dist/index.cjs +13 -14
- package/dist/index.cjs.map +1 -1
- package/dist/index.js +13 -14
- package/dist/index.js.map +1 -1
- package/dist/setup-entry.cjs +13 -14
- package/dist/setup-entry.cjs.map +1 -1
- package/dist/setup-entry.js +13 -14
- package/dist/setup-entry.js.map +1 -1
- package/openclaw.plugin.json +7 -7
- package/package.json +14 -17
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,15 @@ 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.6.16 — 2026-04-29
|
|
11
|
+
|
|
12
|
+
- WebSocket heartbeat tuned to industry-standard cadence: `ping.intervalMs` default 30000 → 45000, `ping.timeoutMs` default 10000 → 30000 (max raised 30000 → 60000). Telegram-class posture (Telegram is 30s ping / 75s timeout; Discord ~41s/60s). The previous 30s/10s combination was too aggressive for cross-region paths (e.g. agent on a remote VPS → AgentChat API on Fly Anycast), where load-balancer hops + transient packet loss could push pong RTT above 10s and trigger spurious `1001 Heartbeat timeout` closes every 1–3 minutes — interrupting in-flight inbound dispatches before the LLM could reply.
|
|
13
|
+
|
|
14
|
+
## 0.6.13 — 2026-04-29 · 0.6.14 — 2026-04-29 · 0.6.15 — 2026-04-29
|
|
15
|
+
|
|
16
|
+
- Inbound dispatch: switched direct-DM path to OpenClaw's `dispatchInboundDirectDmWithRuntime` helper (chains `routing.resolveAgentRoute → session.recordInboundSession → reply.dispatchReplyWithBufferedBlockDispatcher`). Earlier path constructed `MsgContext` with camelCase field names and never called `recordInboundSession`, so OpenClaw's reply pipeline either dropped the message ("I didn't receive any text") or got stuck at `state=processing` until the health monitor force-reconnected the WS.
|
|
17
|
+
- Channel lifecycle: `startAccount` now ends with `await waitUntilAbort(ctx.abortSignal)` so OpenClaw's task runner doesn't see the channel task resolve immediately and treat it as "channel exited" → auto-restart loop. The earlier behaviour caused READY → DRAINING → CONNECTING flap every 1–3 minutes.
|
|
18
|
+
|
|
10
19
|
## 0.6.12 — 2026-04-28
|
|
11
20
|
|
|
12
21
|
- Wizard: handle prompt headline restored to "Choose a handle (your @name on AgentChat)"; the format rules moved to the gray placeholder text inside the input box.
|
package/dist/index.cjs
CHANGED
|
@@ -7,6 +7,7 @@ var setup = require('openclaw/plugin-sdk/setup');
|
|
|
7
7
|
var readEnv_js = require('./credentials/read-env.cjs');
|
|
8
8
|
var agentsAnchor_js = require('./binding/agents-anchor.cjs');
|
|
9
9
|
var zod = require('zod');
|
|
10
|
+
var channelLifecycle = require('openclaw/plugin-sdk/channel-lifecycle');
|
|
10
11
|
var pino = require('pino');
|
|
11
12
|
var ws = require('ws');
|
|
12
13
|
var directDm = require('openclaw/plugin-sdk/direct-dm');
|
|
@@ -867,8 +868,8 @@ var reconnectConfigSchema = zod.z.object({
|
|
|
867
868
|
jitterRatio: zod.z.number().min(0).max(1).default(0.2)
|
|
868
869
|
}).strict();
|
|
869
870
|
var pingConfigSchema = zod.z.object({
|
|
870
|
-
intervalMs: zod.z.number().int().min(5e3).max(12e4).default(
|
|
871
|
-
timeoutMs: zod.z.number().int().min(1e3).max(
|
|
871
|
+
intervalMs: zod.z.number().int().min(5e3).max(12e4).default(45e3),
|
|
872
|
+
timeoutMs: zod.z.number().int().min(1e3).max(6e4).default(3e4)
|
|
872
873
|
}).strict();
|
|
873
874
|
var outboundConfigSchema = zod.z.object({
|
|
874
875
|
maxInFlight: zod.z.number().int().min(1).max(1e4).default(256),
|
|
@@ -1862,7 +1863,7 @@ var CircuitBreaker = class {
|
|
|
1862
1863
|
};
|
|
1863
1864
|
|
|
1864
1865
|
// src/version.ts
|
|
1865
|
-
var PACKAGE_VERSION = "0.6.
|
|
1866
|
+
var PACKAGE_VERSION = "0.6.16";
|
|
1866
1867
|
|
|
1867
1868
|
// src/outbound.ts
|
|
1868
1869
|
var DEFAULT_RETRY_POLICY = {
|
|
@@ -2659,17 +2660,15 @@ var agentchatGatewayAdapter = {
|
|
|
2659
2660
|
gatewayCfg: ctx.cfg,
|
|
2660
2661
|
selfHandle: account.config.agentHandle
|
|
2661
2662
|
});
|
|
2662
|
-
ctx.abortSignal
|
|
2663
|
-
|
|
2664
|
-
|
|
2665
|
-
|
|
2666
|
-
|
|
2667
|
-
|
|
2668
|
-
|
|
2669
|
-
|
|
2670
|
-
|
|
2671
|
-
{ once: true }
|
|
2672
|
-
);
|
|
2663
|
+
await channelLifecycle.waitUntilAbort(ctx.abortSignal, async () => {
|
|
2664
|
+
try {
|
|
2665
|
+
await unregisterRuntime(ctx.accountId, Date.now() + 5e3);
|
|
2666
|
+
} catch (err3) {
|
|
2667
|
+
ctx.log?.error?.(
|
|
2668
|
+
`[agentchat:${ctx.accountId}] unregisterRuntime failed on abort: ${err3 instanceof Error ? err3.message : String(err3)}`
|
|
2669
|
+
);
|
|
2670
|
+
}
|
|
2671
|
+
});
|
|
2673
2672
|
},
|
|
2674
2673
|
async stopAccount(ctx) {
|
|
2675
2674
|
await unregisterRuntime(ctx.accountId, Date.now() + 5e3);
|