nextclaw 0.6.30 → 0.6.32
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "nextclaw",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.32",
|
|
4
4
|
"description": "Lightweight personal AI assistant with CLI, multi-provider routing, and channel integrations.",
|
|
5
5
|
"private": false,
|
|
6
6
|
"type": "module",
|
|
@@ -38,9 +38,9 @@
|
|
|
38
38
|
"dependencies": {
|
|
39
39
|
"chokidar": "^3.6.0",
|
|
40
40
|
"commander": "^12.1.0",
|
|
41
|
-
"@nextclaw/core": "^0.6.
|
|
42
|
-
"@nextclaw/server": "^0.4.
|
|
43
|
-
"@nextclaw/openclaw-compat": "^0.1.
|
|
41
|
+
"@nextclaw/core": "^0.6.25",
|
|
42
|
+
"@nextclaw/server": "^0.4.14",
|
|
43
|
+
"@nextclaw/openclaw-compat": "^0.1.18"
|
|
44
44
|
},
|
|
45
45
|
"devDependencies": {
|
|
46
46
|
"@types/node": "^20.17.6",
|
package/templates/USAGE.md
CHANGED
|
@@ -144,6 +144,8 @@ Restart is still required for:
|
|
|
144
144
|
|
|
145
145
|
To confirm hot reload succeeded, check gateway console logs or `${NEXTCLAW_HOME:-~/.nextclaw}/logs/service.log` for messages like `Config reload: ... applied.`
|
|
146
146
|
|
|
147
|
+
UI note: **Model** page save now persists both `agents.defaults.model` and `agents.defaults.maxTokens` (refresh should keep the updated max token value).
|
|
148
|
+
|
|
147
149
|
### Multi-agent routing & session isolation (OpenClaw-aligned)
|
|
148
150
|
|
|
149
151
|
You can now configure OpenClaw-style multi-agent runtime behavior directly in the UI (**Routing & Runtime**) or in `config.json`:
|
|
@@ -153,6 +155,9 @@ You can now configure OpenClaw-style multi-agent runtime behavior directly in th
|
|
|
153
155
|
- `session.dmScope`: DM isolation strategy (`main` / `per-peer` / `per-channel-peer` / `per-account-channel-peer`)
|
|
154
156
|
- `session.agentToAgent.maxPingPongTurns`: cap cross-agent ping-pong loops (`0` means block auto ping-pong)
|
|
155
157
|
|
|
158
|
+
> ⚠️ **Strict enum guard (OpenClaw-aligned):** `session.dmScope` accepts **only** these 4 values: `main`, `per-peer`, `per-channel-peer`, `per-account-channel-peer`.
|
|
159
|
+
> Any other value (for example `per-account-channel-peer-agent`) is invalid and must not be written.
|
|
160
|
+
|
|
156
161
|
See full architecture details in [Multi-Agent Architecture](guides/multi-agent-architecture.md).
|
|
157
162
|
|
|
158
163
|
Example:
|
|
@@ -325,6 +330,11 @@ For internal AI operations (same as other built-in capabilities):
|
|
|
325
330
|
- Yes, the runtime registers the `gateway` tool (`config.get` / `config.schema` / `config.apply` / `config.patch`).
|
|
326
331
|
- The AI can use it to manage the same config surface when you explicitly ask.
|
|
327
332
|
- As with all config mutations, it follows the explicit-request rule (no silent self-mutation).
|
|
333
|
+
- **Required safe flow for AI config writes:**
|
|
334
|
+
1. run `config.get` to read current config + hash;
|
|
335
|
+
2. run `config.schema` and copy enum values exactly (no invented suffixes/variants);
|
|
336
|
+
3. run `config.patch` with minimal patch;
|
|
337
|
+
4. run `config.get` again to verify persisted value.
|
|
328
338
|
|
|
329
339
|
---
|
|
330
340
|
|