nextclaw 0.5.6 → 0.6.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nextclaw",
-  "version": "0.5.6",
+  "version": "0.6.1",
   "description": "Lightweight personal AI assistant with CLI, multi-provider routing, and channel integrations.",
   "private": false,
   "type": "module",
@@ -38,9 +38,8 @@
   "dependencies": {
     "chokidar": "^3.6.0",
     "commander": "^12.1.0",
-    "@nextclaw/core": "^0.5.3",
-    "@nextclaw/server": "^0.3.7",
-    "@nextclaw/openclaw-compat": "^0.1.4"
+    "@nextclaw/core": "^0.6.1",
+    "@nextclaw/server": "^0.4.1"
   },
   "devDependencies": {
     "@types/node": "^20.17.6",

package/templates/USAGE.md

@@ -8,7 +8,7 @@ This guide covers installation, configuration, channels, tools, automation, and
 
 ## AI Self-Management Contract
 
-When NextClaw AI needs to operate the product itself (status/doctor/plugins/channels/config/cron), follow these rules:
+When NextClaw AI needs to operate the product itself (status/doctor/channels/config/cron), follow these rules:
 
 1. **Read this guide first** (`USAGE.md`) before executing management commands.
 2. **Prefer machine-readable output** (`--json`) whenever available.
@@ -25,7 +25,6 @@ When NextClaw AI needs to operate the product itself (status/doctor/plugins/chan
 - [Configuration](#configuration)
 - [Workspace](#workspace)
 - [Commands](#commands)
-- [Plugins (OpenClaw compatibility)](#plugins-openclaw-compatibility)
 - [Channels](#channels)
 - [Tools](#tools)
 - [Cron & Heartbeat](#cron--heartbeat)
@@ -137,7 +136,6 @@ When the gateway is already running, config changes from the UI or `nextclaw con
 
 Restart is still required for:
 
-- `plugins.*`
 - UI bind port (`--port` / `--ui-port`)
 
 To confirm hot reload succeeded, check gateway console logs or `${NEXTCLAW_HOME:-~/.nextclaw}/logs/service.log` for messages like `Config reload: ... applied.`
@@ -201,7 +199,6 @@ Created under the workspace:
 | `nextclaw channels status` | Show enabled channels and status |
 | `nextclaw doctor` | Run runtime diagnostics (`--json`, `--verbose`, `--fix`) |
 | `nextclaw channels login` | Open QR login for supported channels |
-| `nextclaw channels add --channel <id> [--code/--token/...]` | Run plugin channel setup (OpenClaw-compatible) and write config |
 | `nextclaw cron list` | List scheduled jobs |
 | `nextclaw cron add ...` | Add a cron job (see [Cron](#cron--heartbeat)) |
 | `nextclaw cron remove <jobId>` | Remove a job |
@@ -209,16 +206,9 @@ Created under the workspace:
 | `nextclaw cron run <jobId>` | Run a job once (optionally with `--force` if disabled) |
 | `nextclaw skills install <slug>` | Install a skill from ClawHub |
 | `nextclaw clawhub install <slug>` | Same as `skills install` |
-| `nextclaw plugins list` | List discovered OpenClaw-compatible plugins |
-| `nextclaw plugins info <id>` | Show details of a plugin |
 | `nextclaw config get <path>` | Get config value by path (use `--json` for structured output) |
 | `nextclaw config set <path> <value>` | Set config value by path (use `--json` to parse value as JSON) |
 | `nextclaw config unset <path>` | Remove config value by path |
-| `nextclaw plugins install <path-or-spec>` | Install from local path, archive, or npm package |
-| `nextclaw plugins enable <id>` | Enable a plugin in config |
-| `nextclaw plugins disable <id>` | Disable a plugin in config |
-| `nextclaw plugins uninstall <id>` | Remove plugin config/install record (supports `--dry-run`, `--force`, `--keep-files`) |
-| `nextclaw plugins doctor` | Diagnose plugin load conflicts/errors |
 
 Gateway options (when running `nextclaw gateway` or `nextclaw start`):
 
@@ -237,41 +227,6 @@ Status/diagnostics tips:
 
 ---
 
-## Plugins (OpenClaw compatibility)
-
-NextClaw supports OpenClaw-compatible plugins while keeping compatibility logic isolated in `@nextclaw/openclaw-compat`.
-For architecture boundaries and capability matrix, see [OpenClaw plugin compatibility guide](./openclaw-plugin-compat.md).
-
-Typical flow:
-
-```bash
-# 1) Inspect discovered plugins
-nextclaw plugins list
-
-# 2) Install (path/archive/npm)
-nextclaw plugins install ./my-plugin
-nextclaw plugins install ./my-plugin.tgz
-nextclaw plugins install @scope/openclaw-plugin
-
-# 3) Inspect and toggle
-nextclaw plugins info my-plugin
-nextclaw config get plugins.entries.my-plugin.config --json
-nextclaw plugins disable my-plugin
-nextclaw plugins enable my-plugin
-
-# 4) Uninstall
-nextclaw plugins uninstall my-plugin --dry-run
-nextclaw plugins uninstall my-plugin --force
-```
-
-Notes:
-
-- Plugin config is merged under `plugins.entries.<id>.config`.
-- `plugins uninstall --keep-config` is accepted as a backward-compatible alias of `--keep-files`.
-- If a plugin tool/channel/provider conflicts with a built-in capability, NextClaw rejects the conflicting registration and reports diagnostics.
-
----
-
 ## Self-update
 
 Use the built-in updater:
@@ -312,12 +267,15 @@ Configure channels in the UI at http://127.0.0.1:18791 or in `~/.nextclaw/config
     "discord": {
       "enabled": true,
       "token": "YOUR_BOT_TOKEN",
+      "allowBots": false,
       "allowFrom": []
     }
   }
 }
 ```
 
+- `allowBots` (default `false`): whether to accept bot-authored messages. Keep it `false` unless you explicitly need bot-to-bot flows.
+
 ### Telegram
 
 1. Create a bot via [@BotFather](https://t.me/BotFather) and get the token.
@@ -338,6 +296,11 @@ Configure channels in the UI at http://127.0.0.1:18791 or in `~/.nextclaw/config
 
 Optional: set `"proxy": "http://localhost:7890"` (or your proxy URL) for network access.
 
+Telegram Bot API behavior note:
+
+- In **groups**, bots generally do **not** receive messages from other bots.
+- For bot-to-bot scenarios, prefer **Telegram channels**. NextClaw now processes `channel_post` updates as inbound messages.
+
 ### Slack
 
 Socket mode is the typical setup. You need a **Bot Token** and an **App-Level Token** (with `connections:write`).
@@ -350,6 +313,7 @@ Socket mode is the typical setup. You need a **Bot Token** and an **App-Level To
       "mode": "socket",
       "botToken": "xoxb-...",
       "appToken": "xapp-...",
+      "allowBots": false,
       "dm": { "enabled": true, "allowFrom": [] }
     }
   }
@@ -358,6 +322,7 @@ Socket mode is the typical setup. You need a **Bot Token** and an **App-Level To
 
 - `dm.enabled`: allow DMs to the bot.
 - `dm.allowFrom`: restrict DMs to these user IDs; empty means allow all.
+- `allowBots` (default `false`): whether bot-authored Slack messages can trigger replies.
 
 ### Feishu (Lark)