nextclaw 0.30.0 → 0.31.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nextclaw",
-  "version": "0.30.0",
+  "version": "0.31.0",
   "description": "Powerful AI assistant for coordinating agents, skills, CLI tools, automations, and messaging apps.",
   "private": false,
   "type": "module",
@@ -41,20 +41,20 @@
     "commander": "^12.1.0",
     "jszip": "^3.10.1",
     "yaml": "^2.8.1",
-    "@nextclaw/core": "0.15.21",
-    "@nextclaw/kernel": "0.6.23",
-    "@nextclaw/mcp": "0.3.21",
-    "@nextclaw/ncp": "0.7.16",
-    "@nextclaw/ncp-mcp": "0.2.21",
-    "@nextclaw/ncp-toolkit": "0.6.18",
-    "@nextclaw/nextclaw-ncp-runtime-stdio-client": "0.3.22",
-    "@nextclaw/nextclaw-ncp-runtime-http-client": "0.3.16",
-    "@nextclaw/ncp-agent-runtime": "0.4.16",
-    "@nextclaw/nextclaw-hermes-acp-bridge": "0.3.16",
-    "@nextclaw/runtime": "0.4.21",
-    "@nextclaw/remote": "0.3.23",
-    "@nextclaw/server": "0.15.23",
-    "@nextclaw/service": "0.3.24"
+    "@nextclaw/core": "0.15.22",
+    "@nextclaw/kernel": "0.6.24",
+    "@nextclaw/ncp": "0.7.17",
+    "@nextclaw/mcp": "0.3.22",
+    "@nextclaw/ncp-mcp": "0.2.22",
+    "@nextclaw/ncp-toolkit": "0.6.19",
+    "@nextclaw/nextclaw-hermes-acp-bridge": "0.3.17",
+    "@nextclaw/ncp-agent-runtime": "0.4.17",
+    "@nextclaw/nextclaw-ncp-runtime-http-client": "0.3.17",
+    "@nextclaw/nextclaw-ncp-runtime-stdio-client": "0.3.23",
+    "@nextclaw/remote": "0.3.24",
+    "@nextclaw/runtime": "0.4.22",
+    "@nextclaw/service": "0.3.25",
+    "@nextclaw/server": "0.15.24"
   },
   "devDependencies": {
     "@types/node": "^20.17.6",
@@ -62,7 +62,7 @@
     "tsx": "^4.19.2",
     "typescript": "^5.6.3",
     "vitest": "^4.1.2",
-    "@nextclaw/ui": "0.15.24"
+    "@nextclaw/ui": "0.15.25"
   },
   "scripts": {
     "dev": "tsx watch --tsconfig ../../scripts/dev/dev-runtime.tsconfig.json src/cli/app/index.ts",

package/resources/USAGE.md

@@ -630,7 +630,7 @@ Agent management notes:
   - Without the injection option, the command shows the effective setting.
   - NextClaw context injection is enabled by default. It supplies product instructions, workspace/session context, and the available skill manifest to supported agent runtimes.
   - Codex keeps its native base instructions and receives NextClaw context as developer instructions. Claude Code keeps the `claude_code` preset and receives NextClaw context through the preset's append field.
-  - Changing this runtime setting is saved immediately and requires a gateway restart before new runtime processes use it.
+  - Changing this runtime setting is saved immediately. Run `nextclaw restart` in an external terminal before new runtime processes use it.
 - `nextclaw agents new <agent-id>` accepts:
   - `--name <display-name>`
   - `--description <description>`
@@ -703,7 +703,7 @@ Rules:
 - Do not try to create or remove the built-in `main` agent. `nextclaw agents update main` is allowed.
 - For normal Agent management, prefer `nextclaw agents list|new|update|remove --json` over direct `config.json` or `agents.list` edits.
 - For runtime discovery, prefer `nextclaw agents runtimes --json` over guessing enum values from memory or stale examples.
-- For runtime context injection, prefer `nextclaw agents runtime config <runtime-id>` over direct config edits. Restart the gateway after changing the setting.
+- For runtime context injection, prefer `nextclaw agents runtime config <runtime-id>` over direct config edits. Run `nextclaw restart` in an external terminal after changing the setting.
 - Direct `config.json` / `agents.list` edits are recovery-only: use them only for explicit operator-led disaster recovery, or when a documented CLI path still cannot express the requested change.
 - Humans should use the `Agents` page or the CLI for Agent identities. `Routing & Runtime` is not the identity-management entry point.
 - If the user asked AI to perform Agent CRUD, AI should run the command, not only describe it.
@@ -785,9 +785,9 @@ Behavior:
 - Use `nextclaw update --download-only` to stage an update without switching the active runtime. `nextclaw update --apply` applies an already staged runtime update.
 - If the background service is running, restart it after `nextclaw update` reports that the runtime update was applied.
 - When update is triggered from the running gateway (agent `update.run`), NextClaw arms a self-relaunch helper before exiting, so the service comes back automatically (like an OS reboot flow).
-- After restart, NextClaw automatically pings the last active session with restart/update status (including note when provided).
+- A restart interrupts active conversations. Confirm recovery with `nextclaw status --json` from an external terminal.
 
-If the gateway is running, you can also ask the agent to update; the agent will call the gateway update tool only when you explicitly request it, and restart/relaunch will be scheduled afterward.
+If the gateway is running, you can also ask the agent to update. The agent will call the gateway update tool only when you explicitly request it; the service relaunch is scheduled afterward, but the active conversation can disconnect.
 
 ---