@takibeiy/moltbot_cn 2026.1.27 → 2026.2.1-beta.1

package/docs/platforms/windows.md

@@ -1,12 +1,14 @@
 ---
 summary: "Windows (WSL2) support + companion app status"
 read_when:
-  - Installing Moltbot on Windows
+  - Installing OpenClaw on Windows
   - Looking for Windows companion app status
+title: "Windows (WSL2)"
 ---
+
 # Windows (WSL2)
 
-Moltbot on Windows is recommended **via WSL2** (Ubuntu recommended). The
+OpenClaw on Windows is recommended **via WSL2** (Ubuntu recommended). The
 CLI + Gateway run inside Linux, which keeps the runtime consistent and makes
 tooling far more compatible (Node/Bun/pnpm, Linux binaries, skills). Native
 Windows installs are untested and more problematic.
@@ -14,11 +16,13 @@ Windows installs are untested and more problematic.
 Native Windows companion apps are planned.
 
 ## Install (WSL2)
+
 - [Getting Started](/start/getting-started) (use inside WSL)
 - [Install & updates](/install/updating)
 - Official WSL2 guide (Microsoft): https://learn.microsoft.com/windows/wsl/install
 
 ## Gateway
+
 - [Gateway runbook](/gateway)
 - [Configuration](/gateway/configuration)
 
@@ -27,19 +31,19 @@ Native Windows companion apps are planned.
 Inside WSL2:
 
 ```
-moltbot onboard --install-daemon
+openclaw onboard --install-daemon
 ```
 
 Or:
 
 ```
-moltbot gateway install
+openclaw gateway install
 ```
 
 Or:
 
 ```
-moltbot configure
+openclaw configure
 ```
 
 Select **Gateway service** when prompted.
@@ -47,7 +51,7 @@ Select **Gateway service** when prompted.
 Repair/migrate:
 
 ```
-moltbot doctor
+openclaw doctor
 ```
 
 ## Advanced: expose WSL services over LAN (portproxy)
@@ -87,9 +91,10 @@ netsh interface portproxy add v4tov4 listenport=$ListenPort listenaddress=0.0.0.
 ```
 
 Notes:
+
 - SSH from another machine targets the **Windows host IP** (example: `ssh user@windows-host -p 2222`).
 - Remote nodes must point at a **reachable** Gateway URL (not `127.0.0.1`); use
-  `moltbot status --all` to confirm.
+  `openclaw status --all` to confirm.
 - Use `listenaddress=0.0.0.0` for LAN access; `127.0.0.1` keeps it local only.
 - If you want this automatic, register a Scheduled Task to run the refresh
   step at login.
@@ -132,17 +137,17 @@ Re-open Ubuntu, then verify:
 systemctl --user status
 ```
 
-### 3) Install Moltbot (inside WSL)
+### 3) Install OpenClaw (inside WSL)
 
 Follow the Linux Getting Started flow inside WSL:
 
 ```bash
-git clone https://github.com/moltbot/moltbot.git
-cd moltbot
+git clone https://github.com/openclaw/openclaw.git
+cd openclaw
 pnpm install
 pnpm ui:build # auto-installs UI deps on first run
 pnpm build
-moltbot onboard
+openclaw onboard
 ```
 
 Full guide: [Getting Started](/start/getting-started)

package/docs/plugin.md

@@ -1,55 +1,57 @@
 ---
-summary: "Moltbot plugins/extensions: discovery, config, and safety"
+summary: "OpenClaw plugins/extensions: discovery, config, and safety"
 read_when:
   - Adding or modifying plugins/extensions
   - Documenting plugin install or load rules
+title: "Plugins"
 ---
+
 # Plugins (Extensions)
 
 ## Quick start (new to plugins?)
 
-A plugin is just a **small code module** that extends Moltbot with extra
+A plugin is just a **small code module** that extends OpenClaw with extra
 features (commands, tools, and Gateway RPC).
 
 Most of the time, you’ll use plugins when you want a feature that’s not built
-into core Moltbot yet (or you want to keep optional features out of your main
+into core OpenClaw yet (or you want to keep optional features out of your main
 install).
 
 Fast path:
 
-1) See what’s already loaded:
+1. See what’s already loaded:
 
 ```bash
-moltbot plugins list
+openclaw plugins list
 ```
 
-2) Install an official plugin (example: Voice Call):
+2. Install an official plugin (example: Voice Call):
 
 ```bash
-moltbot plugins install @moltbot/voice-call
+openclaw plugins install @openclaw/voice-call
 ```
 
-3) Restart the Gateway, then configure under `plugins.entries.<id>.config`.
+3. Restart the Gateway, then configure under `plugins.entries.<id>.config`.
 
 See [Voice Call](/plugins/voice-call) for a concrete example plugin.
 
 ## Available plugins (official)
 
-- Microsoft Teams is plugin-only as of 2026.1.15; install `@moltbot/msteams` if you use Teams.
+- Microsoft Teams is plugin-only as of 2026.1.15; install `@openclaw/msteams` if you use Teams.
 - Memory (Core) — bundled memory search plugin (enabled by default via `plugins.slots.memory`)
 - Memory (LanceDB) — bundled long-term memory plugin (auto-recall/capture; set `plugins.slots.memory = "memory-lancedb"`)
-- [Voice Call](/plugins/voice-call) — `@moltbot/voice-call`
-- [Zalo Personal](/plugins/zalouser) — `@moltbot/zalouser`
-- [Matrix](/channels/matrix) — `@moltbot/matrix`
-- [Nostr](/channels/nostr) — `@moltbot/nostr`
-- [Zalo](/channels/zalo) — `@moltbot/zalo`
-- [Microsoft Teams](/channels/msteams) — `@moltbot/msteams`
+- [Voice Call](/plugins/voice-call) — `@openclaw/voice-call`
+- [Zalo Personal](/plugins/zalouser) — `@openclaw/zalouser`
+- [Matrix](/channels/matrix) — `@openclaw/matrix`
+- [Nostr](/channels/nostr) — `@openclaw/nostr`
+- [Zalo](/channels/zalo) — `@openclaw/zalo`
+- [Microsoft Teams](/channels/msteams) — `@openclaw/msteams`
 - Google Antigravity OAuth (provider auth) — bundled as `google-antigravity-auth` (disabled by default)
 - Gemini CLI OAuth (provider auth) — bundled as `google-gemini-cli-auth` (disabled by default)
 - Qwen OAuth (provider auth) — bundled as `qwen-portal-auth` (disabled by default)
 - Copilot Proxy (provider auth) — local VS Code Copilot Proxy bridge; distinct from built-in `github-copilot` device login (bundled, disabled by default)
 
-Moltbot plugins are **TypeScript modules** loaded at runtime via jiti. **Config
+OpenClaw plugins are **TypeScript modules** loaded at runtime via jiti. **Config
 validation does not execute plugin code**; it uses the plugin manifest and JSON
 Schema instead. See [Plugin manifest](/plugins/manifest).
 
@@ -73,39 +75,44 @@ Plugins can access selected core helpers via `api.runtime`. For telephony TTS:
 
 ```ts
 const result = await api.runtime.tts.textToSpeechTelephony({
-  text: "Hello from Moltbot",
+  text: "Hello from OpenClaw",
   cfg: api.config,
 });
 ```
 
 Notes:
+
 - Uses core `messages.tts` configuration (OpenAI or ElevenLabs).
 - Returns PCM audio buffer + sample rate. Plugins must resample/encode for providers.
 - Edge TTS is not supported for telephony.
 
 ## Discovery & precedence
 
-Moltbot scans, in order:
+OpenClaw scans, in order:
+
+1. Config paths
 
-1) Config paths
 - `plugins.load.paths` (file or directory)
 
-2) Workspace extensions
-- `<workspace>/.clawdbot/extensions/*.ts`
-- `<workspace>/.clawdbot/extensions/*/index.ts`
+2. Workspace extensions
+
+- `<workspace>/.openclaw/extensions/*.ts`
+- `<workspace>/.openclaw/extensions/*/index.ts`
+
+3. Global extensions
 
-3) Global extensions
-- `~/.clawdbot/extensions/*.ts`
-- `~/.clawdbot/extensions/*/index.ts`
+- `~/.openclaw/extensions/*.ts`
+- `~/.openclaw/extensions/*/index.ts`
 
-4) Bundled extensions (shipped with Moltbot, **disabled by default**)
-- `<moltbot>/extensions/*`
+4. Bundled extensions (shipped with OpenClaw, **disabled by default**)
+
+- `<openclaw>/extensions/*`
 
 Bundled plugins must be enabled explicitly via `plugins.entries.<id>.enabled`
-or `moltbot plugins enable <id>`. Installed plugins are enabled by default,
+or `openclaw plugins enable <id>`. Installed plugins are enabled by default,
 but can be disabled the same way.
 
-Each plugin must include a `moltbot.plugin.json` file in its root. If a path
+Each plugin must include a `openclaw.plugin.json` file in its root. If a path
 points at a file, the plugin root is the file's directory and must contain the
 manifest.
 
@@ -114,12 +121,12 @@ wins and lower-precedence copies are ignored.
 
 ### Package packs
 
-A plugin directory may include a `package.json` with `moltbot.extensions`:
+A plugin directory may include a `package.json` with `openclaw.extensions`:
 
 ```json
 {
   "name": "my-pack",
-  "moltbot": {
+  "openclaw": {
     "extensions": ["./src/safety.ts", "./src/tools.ts"]
   }
 }
@@ -133,15 +140,15 @@ If your plugin imports npm deps, install them in that directory so
 
 ### Channel catalog metadata
 
-Channel plugins can advertise onboarding metadata via `moltbot.channel` and
-install hints via `moltbot.install`. This keeps the core catalog data-free.
+Channel plugins can advertise onboarding metadata via `openclaw.channel` and
+install hints via `openclaw.install`. This keeps the core catalog data-free.
 
 Example:
 
 ```json
 {
-  "name": "@moltbot/nextcloud-talk",
-  "moltbot": {
+  "name": "@openclaw/nextcloud-talk",
+  "openclaw": {
     "extensions": ["./index.ts"],
     "channel": {
       "id": "nextcloud-talk",
@@ -154,7 +161,7 @@ Example:
       "aliases": ["nc-talk", "nc"]
     },
     "install": {
-      "npmSpec": "@moltbot/nextcloud-talk",
+      "npmSpec": "@openclaw/nextcloud-talk",
       "localPath": "extensions/nextcloud-talk",
       "defaultChoice": "npm"
     }
@@ -162,15 +169,16 @@ Example:
 }
 ```
 
-Moltbot can also merge **external channel catalogs** (for example, an MPM
+OpenClaw can also merge **external channel catalogs** (for example, an MPM
 registry export). Drop a JSON file at one of:
-- `~/.clawdbot/mpm/plugins.json`
-- `~/.clawdbot/mpm/catalog.json`
-- `~/.clawdbot/plugins/catalog.json`
 
-Or point `CLAWDBOT_PLUGIN_CATALOG_PATHS` (or `CLAWDBOT_MPM_CATALOG_PATHS`) at
+- `~/.openclaw/mpm/plugins.json`
+- `~/.openclaw/mpm/catalog.json`
+- `~/.openclaw/plugins/catalog.json`
+
+Or point `OPENCLAW_PLUGIN_CATALOG_PATHS` (or `OPENCLAW_MPM_CATALOG_PATHS`) at
 one or more JSON files (comma/semicolon/`PATH`-delimited). Each file should
-contain `{ "entries": [ { "name": "@scope/pkg", "moltbot": { "channel": {...}, "install": {...} } } ] }`.
+contain `{ "entries": [ { "name": "@scope/pkg", "openclaw": { "channel": {...}, "install": {...} } } ] }`.
 
 ## Plugin IDs
 
@@ -179,7 +187,7 @@ Default plugin ids:
 - Package packs: `package.json` `name`
 - Standalone file: file base name (`~/.../voice-call.ts` → `voice-call`)
 
-If a plugin exports `id`, Moltbot uses it but warns when it doesn’t match the
+If a plugin exports `id`, OpenClaw uses it but warns when it doesn’t match the
 configured id.
 
 ## Config
@@ -192,13 +200,14 @@ configured id.
     deny: ["untrusted-plugin"],
     load: { paths: ["~/Projects/oss/voice-call-extension"] },
     entries: {
-      "voice-call": { enabled: true, config: { provider: "twilio" } }
-    }
-  }
+      "voice-call": { enabled: true, config: { provider: "twilio" } },
+    },
+  },
 }
 ```
 
 Fields:
+
 - `enabled`: master toggle (default: true)
 - `allow`: allowlist (optional)
 - `deny`: denylist (optional; deny wins)
@@ -208,11 +217,12 @@ Fields:
 Config changes **require a gateway restart**.
 
 Validation rules (strict):
+
 - Unknown plugin ids in `entries`, `allow`, `deny`, or `slots` are **errors**.
 - Unknown `channels.<id>` keys are **errors** unless a plugin manifest declares
   the channel id.
 - Plugin config is validated using the JSON Schema embedded in
-  `moltbot.plugin.json` (`configSchema`).
+  `openclaw.plugin.json` (`configSchema`).
 - If a plugin is disabled, its config is preserved and a **warning** is emitted.
 
 ## Plugin slots (exclusive categories)
@@ -224,9 +234,9 @@ Some plugin categories are **exclusive** (only one active at a time). Use
 {
   plugins: {
     slots: {
-      memory: "memory-core" // or "none" to disable memory plugins
-    }
-  }
+      memory: "memory-core", // or "none" to disable memory plugins
+    },
+  },
 }
 ```
 
@@ -237,7 +247,7 @@ are disabled with diagnostics.
 
 The Control UI uses `config.schema` (JSON Schema + `uiHints`) to render better forms.
 
-Moltbot augments `uiHints` at runtime based on discovered plugins:
+OpenClaw augments `uiHints` at runtime based on discovered plugins:
 
 - Adds per-plugin labels for `plugins.entries.<id>` / `.enabled` / `.config`
 - Merges optional plugin-provided config field hints under:
@@ -269,24 +279,24 @@ Example:
 ## CLI
 
 ```bash
-moltbot plugins list
-moltbot plugins info <id>
-moltbot plugins install <path>                 # copy a local file/dir into ~/.clawdbot/extensions/<id>
-moltbot plugins install ./extensions/voice-call # relative path ok
-moltbot plugins install ./plugin.tgz           # install from a local tarball
-moltbot plugins install ./plugin.zip           # install from a local zip
-moltbot plugins install -l ./extensions/voice-call # link (no copy) for dev
-moltbot plugins install @moltbot/voice-call # install from npm
-moltbot plugins update <id>
-moltbot plugins update --all
-moltbot plugins enable <id>
-moltbot plugins disable <id>
-moltbot plugins doctor
+openclaw plugins list
+openclaw plugins info <id>
+openclaw plugins install <path>                 # copy a local file/dir into ~/.openclaw/extensions/<id>
+openclaw plugins install ./extensions/voice-call # relative path ok
+openclaw plugins install ./plugin.tgz           # install from a local tarball
+openclaw plugins install ./plugin.zip           # install from a local zip
+openclaw plugins install -l ./extensions/voice-call # link (no copy) for dev
+openclaw plugins install @openclaw/voice-call # install from npm
+openclaw plugins update <id>
+openclaw plugins update --all
+openclaw plugins enable <id>
+openclaw plugins disable <id>
+openclaw plugins doctor
 ```
 
 `plugins update` only works for npm installs tracked under `plugins.installs`.
 
-Plugins may also register their own top‑level commands (example: `moltbot voicecall`).
+Plugins may also register their own top‑level commands (example: `openclaw voicecall`).
 
 ## Plugin API (overview)
 
@@ -303,7 +313,7 @@ event-driven automation without a separate hook pack install.
 ### Example
 
 ```
-import { registerPluginHooksFromDir } from "moltbot/plugin-sdk";
+import { registerPluginHooksFromDir } from "openclaw/plugin-sdk";
 
 export default function register(api) {
   registerPluginHooksFromDir(api, "./hooks");
@@ -311,20 +321,21 @@ export default function register(api) {
 ```
 
 Notes:
+
 - Hook directories follow the normal hook structure (`HOOK.md` + `handler.ts`).
 - Hook eligibility rules still apply (OS/bins/env/config requirements).
-- Plugin-managed hooks show up in `moltbot hooks list` with `plugin:<id>`.
-- You cannot enable/disable plugin-managed hooks via `moltbot hooks`; enable/disable the plugin instead.
+- Plugin-managed hooks show up in `openclaw hooks list` with `plugin:<id>`.
+- You cannot enable/disable plugin-managed hooks via `openclaw hooks`; enable/disable the plugin instead.
 
 ## Provider plugins (model auth)
 
 Plugins can register **model provider auth** flows so users can run OAuth or
-API-key setup inside Moltbot (no external scripts needed).
+API-key setup inside OpenClaw (no external scripts needed).
 
 Register a provider via `api.registerProvider(...)`. Each provider exposes one
 or more auth methods (OAuth, API key, device code, etc.). These methods power:
 
-- `moltbot models auth login --provider <id> [--method <id>]`
+- `openclaw models auth login --provider <id> [--method <id>]`
 
 Example:
 
@@ -361,6 +372,7 @@ api.registerProvider({
 ```
 
 Notes:
+
 - `run` receives a `ProviderAuthContext` with `prompter`, `runtime`,
   `openUrl`, and `oauth.createVpsAwareHandlers` helpers.
 - Return `configPatch` when you need to add default models or provider config.
@@ -387,7 +399,9 @@ const myChannel = {
   config: {
     listAccountIds: (cfg) => Object.keys(cfg.channels?.acmechat?.accounts ?? {}),
     resolveAccount: (cfg, accountId) =>
-      (cfg.channels?.acmechat?.accounts?.[accountId ?? "default"] ?? { accountId }),
+      cfg.channels?.acmechat?.accounts?.[accountId ?? "default"] ?? {
+        accountId,
+      },
   },
   outbound: {
     deliveryMode: "direct",
@@ -401,6 +415,7 @@ export default function (api) {
 ```
 
 Notes:
+
 - Put config under `channels.<id>` (not `plugins.entries`).
 - `meta.label` is used for labels in CLI/UI lists.
 - `meta.aliases` adds alternate ids for normalization and CLI inputs.
@@ -412,27 +427,32 @@ Notes:
 Use this when you want a **new chat surface** (a “messaging channel”), not a model provider.
 Model provider docs live under `/providers/*`.
 
-1) Pick an id + config shape
+1. Pick an id + config shape
+
 - All channel config lives under `channels.<id>`.
 - Prefer `channels.<id>.accounts.<accountId>` for multi‑account setups.
 
-2) Define the channel metadata
+2. Define the channel metadata
+
 - `meta.label`, `meta.selectionLabel`, `meta.docsPath`, `meta.blurb` control CLI/UI lists.
 - `meta.docsPath` should point at a docs page like `/channels/<id>`.
 - `meta.preferOver` lets a plugin replace another channel (auto-enable prefers it).
 - `meta.detailLabel` and `meta.systemImage` are used by UIs for detail text/icons.
 
-3) Implement the required adapters
+3. Implement the required adapters
+
 - `config.listAccountIds` + `config.resolveAccount`
 - `capabilities` (chat types, media, threads, etc.)
 - `outbound.deliveryMode` + `outbound.sendText` (for basic send)
 
-4) Add optional adapters as needed
+4. Add optional adapters as needed
+
 - `setup` (wizard), `security` (DM policy), `status` (health/diagnostics)
 - `gateway` (start/stop/login), `mentions`, `threading`, `streaming`
 - `actions` (message actions), `commands` (native command behavior)
 
-5) Register the channel in your plugin
+5. Register the channel in your plugin
+
 - `api.registerChannel({ plugin })`
 
 Minimal config example:
@@ -442,10 +462,10 @@ Minimal config example:
   channels: {
     acmechat: {
       accounts: {
-        default: { token: "ACME_TOKEN", enabled: true }
-      }
-    }
-  }
+        default: { token: "ACME_TOKEN", enabled: true },
+      },
+    },
+  },
 }
 ```
 
@@ -466,7 +486,9 @@ const plugin = {
   config: {
     listAccountIds: (cfg) => Object.keys(cfg.channels?.acmechat?.accounts ?? {}),
     resolveAccount: (cfg, accountId) =>
-      (cfg.channels?.acmechat?.accounts?.[accountId ?? "default"] ?? { accountId }),
+      cfg.channels?.acmechat?.accounts?.[accountId ?? "default"] ?? {
+        accountId,
+      },
   },
   outbound: {
     deliveryMode: "direct",
@@ -503,11 +525,14 @@ export default function (api) {
 
 ```ts
 export default function (api) {
-  api.registerCli(({ program }) => {
-    program.command("mycmd").action(() => {
-      console.log("Hello");
-    });
-  }, { commands: ["mycmd"] });
+  api.registerCli(
+    ({ program }) => {
+      program.command("mycmd").action(() => {
+        console.log("Hello");
+      });
+    },
+    { commands: ["mycmd"] },
+  );
 }
 ```
 
@@ -536,7 +561,7 @@ Command handler context:
 - `isAuthorizedSender`: Whether the sender is an authorized user
 - `args`: Arguments passed after the command (if `acceptsArgs: true`)
 - `commandBody`: The full command text
-- `config`: The current Moltbot config
+- `config`: The current OpenClaw config
 
 Command options:
 
@@ -563,6 +588,7 @@ api.registerCommand({
 ```
 
 Notes:
+
 - Plugin commands are processed **before** built-in commands and the AI agent
 - Commands are registered globally and work across all channels
 - Command names are case-insensitive (`/MyStatus` matches `/mystatus`)
@@ -598,14 +624,14 @@ it’s present in your workspace/managed skills locations.
 
 Recommended packaging:
 
-- Main package: `moltbot` (this repo)
-- Plugins: separate npm packages under `@moltbot/*` (example: `@moltbot/voice-call`)
+- Main package: `openclaw` (this repo)
+- Plugins: separate npm packages under `@openclaw/*` (example: `@openclaw/voice-call`)
 
 Publishing contract:
 
-- Plugin `package.json` must include `moltbot.extensions` with one or more entry files.
+- Plugin `package.json` must include `openclaw.extensions` with one or more entry files.
 - Entry files can be `.js` or `.ts` (jiti loads TS at runtime).
-- `moltbot plugins install <npm-spec>` uses `npm pack`, extracts into `~/.clawdbot/extensions/<id>/`, and enables it in config.
+- `openclaw plugins install <npm-spec>` uses `npm pack`, extracts into `~/.openclaw/extensions/<id>/`, and enables it in config.
 - Config key stability: scoped packages are normalized to the **unscoped** id for `plugins.entries.*`.
 
 ## Example plugin: Voice Call
@@ -614,7 +640,7 @@ This repo includes a voice‑call plugin (Twilio or log fallback):
 
 - Source: `extensions/voice-call`
 - Skill: `skills/voice-call`
-- CLI: `moltbot voicecall start|status`
+- CLI: `openclaw voicecall start|status`
 - Tool: `voice_call`
 - RPC: `voicecall.start`, `voicecall.status`
 - Config (twilio): `provider: "twilio"` + `twilio.accountSid/authToken/from` (optional `statusCallbackUrl`, `twimlUrl`)
@@ -635,4 +661,4 @@ Plugins run in-process with the Gateway. Treat them as trusted code:
 Plugins can (and should) ship tests:
 
 - In-repo plugins can keep Vitest tests under `src/**` (example: `src/plugins/voice-call.plugin.test.ts`).
-- Separately published plugins should run their own CI (lint/build/test) and validate `moltbot.extensions` points at the built entrypoint (`dist/index.js`).
+- Separately published plugins should run their own CI (lint/build/test) and validate `openclaw.extensions` points at the built entrypoint (`dist/index.js`).

package/docs/plugins/agent-tools.md

@@ -3,10 +3,12 @@ summary: "Write agent tools in a plugin (schemas, optional tools, allowlists)"
 read_when:
   - You want to add a new agent tool in a plugin
   - You need to make a tool opt-in via allowlists
+title: "Plugin Agent Tools"
 ---
+
 # Plugin agent tools
 
-Moltbot plugins can register **agent tools** (JSON‑schema functions) that are exposed
+OpenClaw plugins can register **agent tools** (JSON‑schema functions) that are exposed
 to the LLM during agent runs. Tools can be **required** (always available) or
 **optional** (opt‑in).
 
@@ -70,18 +72,19 @@ Enable optional tools in `agents.list[].tools.allow` (or global `tools.allow`):
         id: "main",
         tools: {
           allow: [
-            "workflow_tool",  // specific tool name
-            "workflow",       // plugin id (enables all tools from that plugin)
-            "group:plugins"   // all plugin tools
-          ]
-        }
-      }
-    ]
-  }
+            "workflow_tool", // specific tool name
+            "workflow", // plugin id (enables all tools from that plugin)
+            "group:plugins", // all plugin tools
+          ],
+        },
+      },
+    ],
+  },
 }
 ```
 
 Other config knobs that affect tool availability:
+
 - Allowlists that only name plugin tools are treated as plugin opt-ins; core tools remain
   enabled unless you also include core tools or groups in the allowlist.
 - `tools.profile` / `agents.list[].tools.profile` (base allowlist)

package/docs/plugins/manifest.md

@@ -1,13 +1,15 @@
 ---
 summary: "Plugin manifest + JSON schema requirements (strict config validation)"
 read_when:
-  - You are building a Moltbot plugin
+  - You are building a OpenClaw plugin
   - You need to ship a plugin config schema or debug plugin validation errors
+title: "Plugin Manifest"
 ---
-# Plugin manifest (moltbot.plugin.json)
 
-Every plugin **must** ship a `moltbot.plugin.json` file in the **plugin root**.
-Moltbot uses this manifest to validate configuration **without executing plugin
+# Plugin manifest (openclaw.plugin.json)
+
+Every plugin **must** ship a `openclaw.plugin.json` file in the **plugin root**.
+OpenClaw uses this manifest to validate configuration **without executing plugin
 code**. Missing or invalid manifests are treated as plugin errors and block
 config validation.
 
@@ -27,10 +29,12 @@ See the full plugin system guide: [Plugins](/plugin).
 ```
 
 Required keys:
+
 - `id` (string): canonical plugin id.
 - `configSchema` (object): JSON Schema for plugin config (inline).
 
 Optional keys:
+
 - `kind` (string): plugin kind (example: `"memory"`).
 - `channels` (array): channel ids registered by this plugin (example: `["matrix"]`).
 - `providers` (array): provider ids registered by this plugin.
@@ -64,4 +68,4 @@ Optional keys:
   discovery + validation.
 - If your plugin depends on native modules, document the build steps and any
   package-manager allowlist requirements (for example, pnpm `allow-build-scripts`
-  + `pnpm rebuild <package>`).
+  - `pnpm rebuild <package>`).