@gguf/pigbot 0.0.6 → 0.0.7

package/docs/platforms/raspberry-pi.md

@@ -1,16 +1,16 @@
 ---
-summary: "Moltbot on Raspberry Pi (budget self-hosted setup)"
+summary: "OpenClaw on Raspberry Pi (budget self-hosted setup)"
 read_when:
-  - Setting up Moltbot on a Raspberry Pi
-  - Running Moltbot on ARM devices
+  - Setting up OpenClaw on a Raspberry Pi
+  - Running OpenClaw on ARM devices
   - Building a cheap always-on personal AI
 ---
 
-# Moltbot on Raspberry Pi
+# OpenClaw on Raspberry Pi
 
 ## Goal
 
-Run a persistent, always-on Moltbot Gateway on a Raspberry Pi for **~$35-80** one-time cost (no monthly fees).
+Run a persistent, always-on OpenClaw Gateway on a Raspberry Pi for **~$35-80** one-time cost (no monthly fees).
 
 Perfect for:
 - 24/7 personal AI assistant
@@ -105,19 +105,19 @@ echo 'vm.swappiness=10' | sudo tee -a /etc/sysctl.conf
 sudo sysctl -p
 ```
 
-## 6) Install Moltbot
+## 6) Install OpenClaw
 
 ### Option A: Standard Install (Recommended)
 
 ```bash
-curl -fsSL https://molt.bot/install.sh | bash
+curl -fsSL https://openclaw.bot/install.sh | bash
 ```
 
 ### Option B: Hackable Install (For tinkering)
 
 ```bash
-git clone https://github.com/moltbot/moltbot.git
-cd moltbot
+git clone https://github.com/openclaw/openclaw.git
+cd openclaw
 npm install
 npm run build
 npm link
@@ -128,7 +128,7 @@ The hackable install gives you direct access to logs and code — useful for deb
 ## 7) Run Onboarding
 
 ```bash
-moltbot onboard --install-daemon
+openclaw onboard --install-daemon
 ```
 
 Follow the wizard:
@@ -141,13 +141,13 @@ Follow the wizard:
 
 ```bash
 # Check status
-moltbot status
+openclaw status
 
 # Check service
-sudo systemctl status moltbot
+sudo systemctl status openclaw
 
 # View logs
-journalctl -u moltbot -f
+journalctl -u openclaw -f
 ```
 
 ## 9) Access the Dashboard
@@ -170,8 +170,8 @@ curl -fsSL https://tailscale.com/install.sh | sh
 sudo tailscale up
 
 # Update config
-moltbot config set gateway.bind tailnet
-sudo systemctl restart moltbot
+openclaw config set gateway.bind tailnet
+sudo systemctl restart openclaw
 ```
 
 ---
@@ -218,7 +218,7 @@ htop
 
 ### Binary Compatibility
 
-Most Moltbot features work on ARM64, but some external binaries may need ARM builds:
+Most OpenClaw features work on ARM64, but some external binaries may need ARM builds:
 
 | Tool | ARM64 Status | Notes |
 |------|--------------|-------|
@@ -268,13 +268,13 @@ The onboarding wizard sets this up, but to verify:
 
 ```bash
 # Check service is enabled
-sudo systemctl is-enabled moltbot
+sudo systemctl is-enabled openclaw
 
 # Enable if not
-sudo systemctl enable moltbot
+sudo systemctl enable openclaw
 
 # Start on boot
-sudo systemctl start moltbot
+sudo systemctl start openclaw
 ```
 
 ---
@@ -301,12 +301,12 @@ free -h
 
 ```bash
 # Check logs
-journalctl -u moltbot --no-pager -n 100
+journalctl -u openclaw --no-pager -n 100
 
 # Common fix: rebuild
-cd ~/moltbot  # if using hackable install
+cd ~/openclaw  # if using hackable install
 npm run build
-sudo systemctl restart moltbot
+sudo systemctl restart openclaw
 ```
 
 ### ARM Binary Issues

package/docs/platforms/windows.md

@@ -1,12 +1,12 @@
 ---
 summary: "Windows (WSL2) support + companion app status"
 read_when:
-  - Installing Moltbot on Windows
+  - Installing OpenClaw on Windows
   - Looking for Windows companion app status
 ---
 # 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.
@@ -27,19 +27,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 +47,7 @@ Select **Gateway service** when prompted.
 Repair/migrate:
 
 ```
-moltbot doctor
+openclaw doctor
 ```
 
 ## Advanced: expose WSL services over LAN (portproxy)
@@ -89,7 +89,7 @@ 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 +132,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,5 +1,5 @@
 ---
-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
@@ -8,11 +8,11 @@ read_when:
 
 ## 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:
@@ -20,13 +20,13 @@ Fast path:
 1) See what’s already loaded:
 
 ```bash
-moltbot plugins list
+openclaw plugins list
 ```
 
 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`.
@@ -35,21 +35,21 @@ 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,7 +73,7 @@ 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,
 });
 ```
@@ -85,27 +85,27 @@ Notes:
 
 ## Discovery & precedence
 
-Moltbot scans, in order:
+OpenClaw scans, in order:
 
 1) Config paths
 - `plugins.load.paths` (file or directory)
 
 2) Workspace extensions
-- `<workspace>/.clawdbot/extensions/*.ts`
-- `<workspace>/.clawdbot/extensions/*/index.ts`
+- `<workspace>/.openclaw/extensions/*.ts`
+- `<workspace>/.openclaw/extensions/*/index.ts`
 
 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 +114,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 +133,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 +154,7 @@ Example:
       "aliases": ["nc-talk", "nc"]
     },
     "install": {
-      "npmSpec": "@moltbot/nextcloud-talk",
+      "npmSpec": "@openclaw/nextcloud-talk",
       "localPath": "extensions/nextcloud-talk",
       "defaultChoice": "npm"
     }
@@ -162,15 +162,15 @@ 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`
+- `~/.openclaw/mpm/plugins.json`
+- `~/.openclaw/mpm/catalog.json`
+- `~/.openclaw/plugins/catalog.json`
 
-Or point `CLAWDBOT_PLUGIN_CATALOG_PATHS` (or `CLAWDBOT_MPM_CATALOG_PATHS`) at
+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 +179,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
@@ -212,7 +212,7 @@ Validation rules (strict):
 - 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)
@@ -237,7 +237,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 +269,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 +303,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");
@@ -313,18 +313,18 @@ 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:
 
@@ -536,7 +536,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:
 
@@ -598,14 +598,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 +614,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 +635,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

@@ -6,7 +6,7 @@ read_when:
 ---
 # 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).
 

package/docs/plugins/manifest.md

@@ -1,13 +1,13 @@
 ---
 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
 ---
-# Plugin manifest (moltbot.plugin.json)
+# Plugin manifest (openclaw.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
+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.
 

package/docs/plugins/voice-call.md

@@ -1,13 +1,13 @@
 ---
 summary: "Voice Call plugin: outbound + inbound calls via Twilio/Telnyx/Plivo (plugin install + config + CLI)"
 read_when:
-  - You want to place an outbound voice call from Moltbot
+  - You want to place an outbound voice call from OpenClaw
   - You are configuring or developing the voice-call plugin
 ---
 
 # Voice Call (plugin)
 
-Voice calls for Moltbot via a plugin. Supports outbound notifications and
+Voice calls for OpenClaw via a plugin. Supports outbound notifications and
 multi-turn conversations with inbound policies.
 
 Current providers:
@@ -20,7 +20,7 @@ Quick mental model:
 - Install plugin
 - Restart Gateway
 - Configure under `plugins.entries.voice-call.config`
-- Use `moltbot voicecall ...` or the `voice_call` tool
+- Use `openclaw voicecall ...` or the `voice_call` tool
 
 ## Where it runs (local vs remote)
 
@@ -33,7 +33,7 @@ If you use a remote Gateway, install/configure the plugin on the **machine runni
 ### Option A: install from npm (recommended)
 
 ```bash
-moltbot plugins install @moltbot/voice-call
+openclaw plugins install @openclaw/voice-call
 ```
 
 Restart the Gateway afterwards.
@@ -41,7 +41,7 @@ Restart the Gateway afterwards.
 ### Option B: install from a local folder (dev, no copying)
 
 ```bash
-moltbot plugins install ./extensions/voice-call
+openclaw plugins install ./extensions/voice-call
 cd ./extensions/voice-call && pnpm install
 ```
 
@@ -208,13 +208,13 @@ Auto-responses use the agent system. Tune with:
 ## CLI
 
 ```bash
-moltbot voicecall call --to "+15555550123" --message "Hello from Moltbot"
-moltbot voicecall continue --call-id <id> --message "Any questions?"
-moltbot voicecall speak --call-id <id> --message "One moment"
-moltbot voicecall end --call-id <id>
-moltbot voicecall status --call-id <id>
-moltbot voicecall tail
-moltbot voicecall expose --mode funnel
+openclaw voicecall call --to "+15555550123" --message "Hello from OpenClaw"
+openclaw voicecall continue --call-id <id> --message "Any questions?"
+openclaw voicecall speak --call-id <id> --message "One moment"
+openclaw voicecall end --call-id <id>
+openclaw voicecall status --call-id <id>
+openclaw voicecall tail
+openclaw voicecall expose --mode funnel
 ```
 
 ## Agent tool

package/docs/plugins/zalouser.md

@@ -1,13 +1,13 @@
 ---
 summary: "Zalo Personal plugin: QR login + messaging via zca-cli (plugin install + channel config + CLI + tool)"
 read_when:
-  - You want Zalo Personal (unofficial) support in Moltbot
+  - You want Zalo Personal (unofficial) support in OpenClaw
   - You are configuring or developing the zalouser plugin
 ---
 
 # Zalo Personal (plugin)
 
-Zalo Personal support for Moltbot via a plugin, using `zca-cli` to automate a normal Zalo user account.
+Zalo Personal support for OpenClaw via a plugin, using `zca-cli` to automate a normal Zalo user account.
 
 > **Warning:** Unofficial automation may lead to account suspension/ban. Use at your own risk.
 
@@ -24,7 +24,7 @@ If you use a remote Gateway, install/configure it on the **machine running the G
 ### Option A: install from npm
 
 ```bash
-moltbot plugins install @moltbot/zalouser
+openclaw plugins install @openclaw/zalouser
 ```
 
 Restart the Gateway afterwards.
@@ -32,7 +32,7 @@ Restart the Gateway afterwards.
 ### Option B: install from a local folder (dev)
 
 ```bash
-moltbot plugins install ./extensions/zalouser
+openclaw plugins install ./extensions/zalouser
 cd ./extensions/zalouser && pnpm install
 ```
 
@@ -62,11 +62,11 @@ Channel config lives under `channels.zalouser` (not `plugins.entries.*`):
 ## CLI
 
 ```bash
-moltbot channels login --channel zalouser
-moltbot channels logout --channel zalouser
-moltbot channels status --probe
-moltbot message send --channel zalouser --target <threadId> --message "Hello from Moltbot"
-moltbot directory peers list --channel zalouser --query "name"
+openclaw channels login --channel zalouser
+openclaw channels logout --channel zalouser
+openclaw channels status --probe
+openclaw message send --channel zalouser --target <threadId> --message "Hello from OpenClaw"
+openclaw directory peers list --channel zalouser --query "name"
 ```
 
 ## Agent tool