nextclaw 0.44.0 → 0.44.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nextclaw",
-  "version": "0.44.0",
+  "version": "0.44.2",
   "description": "Powerful AI assistant for coordinating agents, skills, CLI tools, automations, and messaging apps.",
   "private": false,
   "type": "module",
@@ -41,21 +41,22 @@
     "commander": "^12.1.0",
     "jszip": "^3.10.1",
     "yaml": "^2.8.1",
-    "@nextclaw/app-runtime": "0.13.2",
-    "@nextclaw/core": "0.17.9",
-    "@nextclaw/kernel": "0.10.2",
-    "@nextclaw/mcp": "0.3.36",
-    "@nextclaw/ncp-agent-runtime": "0.4.21",
+    "@nextclaw/core": "0.17.11",
+    "@nextclaw/mcp": "0.3.38",
+    "@nextclaw/app-runtime": "0.13.3",
+    "@nextclaw/kernel": "0.11.0",
     "@nextclaw/ncp": "0.10.0",
-    "@nextclaw/ncp-mcp": "0.2.36",
+    "@nextclaw/ncp-agent-runtime": "0.4.21",
+    "@nextclaw/ncp-mcp": "0.2.38",
     "@nextclaw/ncp-toolkit": "0.6.23",
     "@nextclaw/nextclaw-hermes-acp-bridge": "0.3.21",
     "@nextclaw/nextclaw-ncp-runtime-http-client": "0.3.22",
-    "@nextclaw/nextclaw-ncp-runtime-stdio-client": "0.3.36",
-    "@nextclaw/remote": "0.3.44",
-    "@nextclaw/runtime": "0.4.35",
-    "@nextclaw/server": "0.18.2",
-    "@nextclaw/service": "0.3.47"
+    "@nextclaw/nextclaw-ncp-runtime-stdio-client": "0.3.38",
+    "@nextclaw/remote": "0.3.46",
+    "@nextclaw/runtime": "0.4.37",
+    "@nextclaw/service": "0.3.49",
+    "@nextclaw/server": "0.19.0",
+    "@nextclaw/shared": "0.4.29"
   },
   "devDependencies": {
     "@types/node": "^20.17.6",
@@ -63,7 +64,7 @@
     "tsx": "^4.19.2",
     "typescript": "^5.6.3",
     "vitest": "^4.1.2",
-    "@nextclaw/ui": "0.20.2"
+    "@nextclaw/ui": "0.21.0"
   },
   "scripts": {
     "dev": "tsx watch --tsconfig ../../scripts/dev/dev-runtime.tsconfig.json src/cli/app/index.ts",

package/resources/USAGE.md

@@ -20,6 +20,7 @@ When NextClaw AI needs to operate the product itself (version/status/doctor/serv
 8. **Desktop-installed AI uses the same command names**. When NextClaw Desktop launches the runtime, it exposes a managed `nextclaw` command surface to AI command tools, so self-management commands keep using `nextclaw ...` without requiring a global NPM install.
 9. **Restart live Service App runtimes before live retest**: after modifying a running Service App, use `nextclaw app restart <app-id> --json` before validating through the product UI or panel-to-service action calls.
 10. **Manage App data through the product contract**: list data with `nextclaw app data list --json`; delete only a `retained` entry with the returned data id and an exact `--confirm <app-id>`. Never replace this flow with a recursive filesystem deletion.
+11. **Manage Mini Apps through the product contract**: use `nextclaw app install <app-id|local-dir|bundle.napp>`, `list`, `operations`, `enable`, `disable`, `update`, `rollback`, and `uninstall`. Do not use or recommend another App runtime command.
 
 ---
 
@@ -35,6 +36,7 @@ When NextClaw AI needs to operate the product itself (version/status/doctor/serv
 - [Session management (UI)](#session-management-ui)
 - [Workspace](#workspace)
 - [Publishing Mini Apps](#publishing-mini-apps)
+- [Managing Mini Apps](#managing-mini-apps)
 - [App data and uninstall](#app-data-and-uninstall)
 - [Commands](#commands)
 - [Channels](#channels)
@@ -463,6 +465,9 @@ nextclaw projects create knowledge --path ~/Projects/knowledge --template knowle
 nextclaw sessions rename <session-id> "Research session" --json
 nextclaw sessions set-project <session-id> ~/Projects/research --json
 nextclaw sessions clear-project <session-id> --json
+
+# Permanently delete a session (the confirmation must match the session ID)
+nextclaw sessions delete <session-id> --confirm <session-id> --json
 ```
 
 The UI, CLI, and built-in AI tools all use the same kernel-owned operations. AI exposes them through `projects_list`, `projects_create`, and `sessions_update`. Project creation never overwrites a non-empty directory. Binding an existing directory registers it as a project; binding the default workspace clears the explicit project binding instead.
@@ -473,7 +478,7 @@ This is useful when running multi-agent routing and channel operations long term
 
 NextClaw UI includes a first-class **Chat** tab so you can talk to your agent directly from browser:
 
-- create/switch/delete sessions from the left panel
+- create, switch, rename, pin, or delete sessions from the left panel; press Enter to confirm a deletion or Escape to cancel
 - filter session list by channel in the left panel
 - inspect complete session history in the thread panel
 - choose target agent before sending message
@@ -574,6 +579,22 @@ After validation succeeds, submit the package for review:
 nextclaw app publish <mini-app-dir> --json
 ```
 
+## Managing Mini Apps
+
+Use the same NextClaw command surface for Marketplace Apps, local App directories, and local `.napp` bundles. The Marketplace keeps an App identifier and registry location; its displayed installation command is derived by NextClaw, not stored per App.
+
+```bash
+nextclaw app marketplace search --query notes --json
+nextclaw app marketplace info nextclaw.personal-organizer --json
+nextclaw app install nextclaw.personal-organizer --json
+nextclaw app install ./my-local-app --json
+nextclaw app install ./release/my-local-app.napp --json
+nextclaw app operations --json
+nextclaw app enable nextclaw.personal-organizer --json
+```
+
+Install, update, rollback, and uninstall return a background operation receipt. Check `nextclaw app operations --json` or the Apps page for progress. Schema v2 Apps remain disabled after installation until explicitly enabled.
+
 Personal submissions return `publishStatus: pending` and appear in the public App Marketplace only after approval with `catalogVisibility: listed`. Community Panel-only Apps follow normal review. Schema v2 Service components currently launch host processes with the user's permissions, so their root manifest must declare `runtime.profile: native-process` and enter high-privilege manual review; an administrator may approve them as `listed` or `unlisted`. Installed schema v2 Apps remain disabled until the user explicitly enables them. Schema v2 WASI Service components are not supported yet—changing only the profile does not create a sandbox. Pending or rejected submissions can be corrected and submitted again. Updating an already published personal app is intentionally blocked until version-level review is available, so the current public version remains online.
 
 Use `https://platform.nextclaw.io/apps` to review submission status. The built-in `nextclaw-app-publisher` skill lets NextClaw AI assemble a package from existing Panel/Service directories, run the checks, guide login, and submit it with the same native commands.
@@ -623,11 +644,11 @@ nextclaw app data list --json
 
 The second list verifies that the retained entry is gone. Do not build a data id manually and do not remove managed directories with `rm -rf`.
 
-For the low-level NApp runtime, uninstall keeps data unless `--purge-data` is present:
+Uninstall keeps data unless `--purge-data` is present:
 
 ```bash
-napp uninstall <app-id>
-napp uninstall <app-id> --purge-data
+nextclaw app uninstall <app-id>
+nextclaw app uninstall <app-id> --purge-data --confirm <app-id>
 ```
 
 Service App development gets a separate, deterministic development instance. Resetting it is destructive and therefore requires both the reset flag and an exact manifest id confirmation:
@@ -655,6 +676,17 @@ nextclaw app dev <service-app-dir> --reset-data --confirm <app-id> --json
 | `nextclaw app validate-publish <mini-app-dir>` | Validate a schema v2 Mini App package before Marketplace submission |
 | `nextclaw app publish <mini-app-dir>` | Submit a validated Mini App to the App Marketplace for review |
 | `nextclaw app restart <app-id>` | Restart a live Service App runtime in the running UI before live retest |
+| `nextclaw app marketplace search` | Search Apps available from the official App Marketplace |
+| `nextclaw app marketplace info <app-id>` | Show a Marketplace App and its derived installation command |
+| `nextclaw app list` | List Apps installed in the running NextClaw host |
+| `nextclaw app info <app-id>` | Show the installed App state and versions |
+| `nextclaw app operations` | List durable App lifecycle operations |
+| `nextclaw app install <app-id\|local-dir\|bundle.napp>` | Install an App through the running host |
+| `nextclaw app enable <app-id>` | Enable an installed App |
+| `nextclaw app disable <app-id>` | Disable an installed App |
+| `nextclaw app update <app-id>` | Start a background App update |
+| `nextclaw app rollback <app-id> --version <version>` | Roll back to an installed version |
+| `nextclaw app uninstall <app-id>` | Start a background uninstall; require exact confirmation to purge data |
 | `nextclaw service install-systemd --user` | Install a user-level Linux `systemd` service for NextClaw |
 | `sudo nextclaw service install-systemd --system` | Install a system-wide Linux `systemd` service for NextClaw |
 | `nextclaw service uninstall-systemd --user` | Remove a user-level Linux `systemd` service |

package/resources/apps/nextclaw-personal-organizer/README.md

@@ -18,7 +18,7 @@ Data is stored locally under NextClaw's app data directory. Each panel only decl
 Personal Space is built into supported NextClaw releases. It can also be installed from the official Apps Registry:
 
 ```bash
-napp install nextclaw.personal-organizer
+nextclaw app install nextclaw.personal-organizer
 ```
 
 After installation, open **Apps** in NextClaw and enable Personal Space. You can then launch Todos, Notes, Favorites, or Calendar independently.