@gguf/pigbot 0.0.6 → 0.0.7

package/docs/tools/browser.md

@@ -2,29 +2,29 @@
 summary: "Integrated browser control service + action commands"
 read_when:
   - Adding agent-controlled browser automation
-  - Debugging why clawd is interfering with your own Chrome
+  - Debugging why openclaw is interfering with your own Chrome
   - Implementing browser settings + lifecycle in the macOS app
 ---
 
-# Browser (clawd-managed)
+# Browser (openclaw-managed)
 
-Moltbot can run a **dedicated Chrome/Brave/Edge/Chromium profile** that the agent controls.
+OpenClaw can run a **dedicated Chrome/Brave/Edge/Chromium profile** that the agent controls.
 It is isolated from your personal browser and is managed through a small local
 control service inside the Gateway (loopback only).
 
 Beginner view:
 - Think of it as a **separate, agent-only browser**.
-- The `clawd` profile does **not** touch your personal browser profile.
+- The `openclaw` profile does **not** touch your personal browser profile.
 - The agent can **open tabs, read pages, click, and type** in a safe lane.
 - The default `chrome` profile uses the **system default Chromium browser** via the
-  extension relay; switch to `clawd` for the isolated managed browser.
+  extension relay; switch to `openclaw` for the isolated managed browser.
 
 ## What you get
 
-- A separate browser profile named **clawd** (orange accent by default).
+- A separate browser profile named **openclaw** (orange accent by default).
 - Deterministic tab control (list/open/focus/close).
 - Agent actions (click/type/drag/select), snapshots, screenshots, PDFs.
-- Optional multi-profile support (`clawd`, `work`, `remote`, ...).
+- Optional multi-profile support (`openclaw`, `work`, `remote`, ...).
 
 This browser is **not** your daily driver. It is a safe, isolated surface for
 agent automation and verification.
@@ -32,26 +32,26 @@ agent automation and verification.
 ## Quick start
 
 ```bash
-moltbot browser --browser-profile clawd status
-moltbot browser --browser-profile clawd start
-moltbot browser --browser-profile clawd open https://example.com
-moltbot browser --browser-profile clawd snapshot
+openclaw browser --browser-profile openclaw status
+openclaw browser --browser-profile openclaw start
+openclaw browser --browser-profile openclaw open https://example.com
+openclaw browser --browser-profile openclaw snapshot
 ```
 
 If you get “Browser disabled”, enable it in config (see below) and restart the
 Gateway.
 
-## Profiles: `clawd` vs `chrome`
+## Profiles: `openclaw` vs `chrome`
 
-- `clawd`: managed, isolated browser (no extension required).
-- `chrome`: extension relay to your **system browser** (requires the Moltbot
+- `openclaw`: managed, isolated browser (no extension required).
+- `chrome`: extension relay to your **system browser** (requires the OpenClaw
   extension to be attached to a tab).
 
-Set `browser.defaultProfile: "clawd"` if you want managed mode by default.
+Set `browser.defaultProfile: "openclaw"` if you want managed mode by default.
 
 ## Configuration
 
-Browser settings live in `~/.clawdbot/moltbot.json`.
+Browser settings live in `~/.openclaw/openclaw.json`.
 
 ```json5
 {
@@ -67,7 +67,7 @@ Browser settings live in `~/.clawdbot/moltbot.json`.
     attachOnly: false,
     executablePath: "/Applications/Brave Browser.app/Contents/MacOS/Brave Browser",
     profiles: {
-      clawd: { cdpPort: 18800, color: "#FF4500" },
+      openclaw: { cdpPort: 18800, color: "#FF4500" },
       work: { cdpPort: 18801, color: "#0066CC" },
       remote: { cdpUrl: "http://10.0.0.42:9222", color: "#00AA00" }
     }
@@ -78,27 +78,27 @@ Browser settings live in `~/.clawdbot/moltbot.json`.
 Notes:
 - The browser control service binds to loopback on a port derived from `gateway.port`
   (default: `18791`, which is gateway + 2). The relay uses the next port (`18792`).
-- If you override the Gateway port (`gateway.port` or `CLAWDBOT_GATEWAY_PORT`),
+- If you override the Gateway port (`gateway.port` or `OPENCLAW_GATEWAY_PORT`),
   the derived browser ports shift to stay in the same “family”.
 - `cdpUrl` defaults to the relay port when unset.
 - `remoteCdpTimeoutMs` applies to remote (non-loopback) CDP reachability checks.
 - `remoteCdpHandshakeTimeoutMs` applies to remote CDP WebSocket reachability checks.
 - `attachOnly: true` means “never launch a local browser; only attach if it is already running.”
 - `color` + per-profile `color` tint the browser UI so you can see which profile is active.
-- Default profile is `chrome` (extension relay). Use `defaultProfile: "clawd"` for the managed browser.
+- Default profile is `chrome` (extension relay). Use `defaultProfile: "openclaw"` for the managed browser.
 - Auto-detect order: system default browser if Chromium-based; otherwise Chrome → Brave → Edge → Chromium → Chrome Canary.
-- Local `clawd` profiles auto-assign `cdpPort`/`cdpUrl` — set those only for remote CDP.
+- Local `openclaw` profiles auto-assign `cdpPort`/`cdpUrl` — set those only for remote CDP.
 
 ## Use Brave (or another Chromium-based browser)
 
 If your **system default** browser is Chromium-based (Chrome/Brave/Edge/etc),
-Moltbot uses it automatically. Set `browser.executablePath` to override
+OpenClaw uses it automatically. Set `browser.executablePath` to override
 auto-detection:
 
 CLI example:
 
 ```bash
-moltbot config set browser.executablePath "/usr/bin/google-chrome"
+openclaw config set browser.executablePath "/usr/bin/google-chrome"
 ```
 
 ```json5
@@ -129,19 +129,19 @@ moltbot config set browser.executablePath "/usr/bin/google-chrome"
 - **Local control (default):** the Gateway starts the loopback control service and can launch a local browser.
 - **Remote control (node host):** run a node host on the machine that has the browser; the Gateway proxies browser actions to it.
 - **Remote CDP:** set `browser.profiles.<name>.cdpUrl` (or `browser.cdpUrl`) to
-  attach to a remote Chromium-based browser. In this case, Moltbot will not launch a local browser.
+  attach to a remote Chromium-based browser. In this case, OpenClaw will not launch a local browser.
 
 Remote CDP URLs can include auth:
 - Query tokens (e.g., `https://provider.example?token=<token>`)
 - HTTP Basic auth (e.g., `https://user:pass@provider.example`)
 
-Moltbot preserves the auth when calling `/json/*` endpoints and when connecting
+OpenClaw preserves the auth when calling `/json/*` endpoints and when connecting
 to the CDP WebSocket. Prefer environment variables or secrets managers for
 tokens instead of committing them to config files.
 
 ## Node browser proxy (zero-config default)
 
-If you run a **node host** on the machine that has your browser, Moltbot can
+If you run a **node host** on the machine that has your browser, OpenClaw can
 auto-route browser tool calls to that node without any extra browser config.
 This is the default path for remote gateways.
 
@@ -155,7 +155,7 @@ Notes:
 ## Browserless (hosted remote CDP)
 
 [Browserless](https://browserless.io) is a hosted Chromium service that exposes
-CDP endpoints over HTTPS. You can point a Moltbot browser profile at a
+CDP endpoints over HTTPS. You can point a OpenClaw browser profile at a
 Browserless region endpoint and authenticate with your API key.
 
 Example:
@@ -193,13 +193,13 @@ Remote CDP tips:
 
 ## Profiles (multi-browser)
 
-Moltbot supports multiple named profiles (routing configs). Profiles can be:
-- **clawd-managed**: a dedicated Chromium-based browser instance with its own user data directory + CDP port
+OpenClaw supports multiple named profiles (routing configs). Profiles can be:
+- **openclaw-managed**: a dedicated Chromium-based browser instance with its own user data directory + CDP port
 - **remote**: an explicit CDP URL (Chromium-based browser running elsewhere)
 - **extension relay**: your existing Chrome tab(s) via the local relay + Chrome extension
 
 Defaults:
-- The `clawd` profile is auto-created if missing.
+- The `openclaw` profile is auto-created if missing.
 - The `chrome` profile is built-in for the Chrome extension relay (points at `http://127.0.0.1:18792` by default).
 - Local CDP ports allocate from **18800–18899** by default.
 - Deleting a profile moves its local data directory to Trash.
@@ -208,14 +208,14 @@ All control endpoints accept `?profile=<name>`; the CLI uses `--browser-profile`
 
 ## Chrome extension relay (use your existing Chrome)
 
-Moltbot can also drive **your existing Chrome tabs** (no separate “clawd” Chrome instance) via a local CDP relay + a Chrome extension.
+OpenClaw can also drive **your existing Chrome tabs** (no separate “openclaw” Chrome instance) via a local CDP relay + a Chrome extension.
 
 Full guide: [Chrome extension](/tools/chrome-extension)
 
 Flow:
 - The Gateway runs locally (same machine) or a node host runs on the browser machine.
 - A local **relay server** listens at a loopback `cdpUrl` (default: `http://127.0.0.1:18792`).
-- You click the **Moltbot Browser Relay** extension icon on a tab to attach (it does not auto-attach).
+- You click the **OpenClaw Browser Relay** extension icon on a tab to attach (it does not auto-attach).
 - The agent controls that tab via the normal `browser` tool, by selecting the right profile.
 
 If the Gateway runs elsewhere, run a node host on the browser machine so the Gateway can proxy browser actions.
@@ -232,21 +232,21 @@ Chrome extension relay takeover requires host browser control, so either:
 1) Load the extension (dev/unpacked):
 
 ```bash
-moltbot browser extension install
+openclaw browser extension install
 ```
 
 - Chrome → `chrome://extensions` → enable “Developer mode”
-- “Load unpacked” → select the directory printed by `moltbot browser extension path`
+- “Load unpacked” → select the directory printed by `openclaw browser extension path`
 - Pin the extension, then click it on the tab you want to control (badge shows `ON`).
 
 2) Use it:
-- CLI: `moltbot browser --browser-profile chrome tabs`
+- CLI: `openclaw browser --browser-profile chrome tabs`
 - Agent tool: `browser` with `profile="chrome"`
 
 Optional: if you want a different name or relay port, create your own profile:
 
 ```bash
-moltbot browser create-profile \
+openclaw browser create-profile \
   --name my-chrome \
   --driver extension \
   --cdp-url http://127.0.0.1:18792 \
@@ -265,7 +265,7 @@ Notes:
 
 ## Browser selection
 
-When launching locally, Moltbot picks the first available:
+When launching locally, OpenClaw picks the first available:
 1. Chrome
 2. Brave
 3. Edge
@@ -302,12 +302,12 @@ All endpoints accept `?profile=<name>`.
 
 Some features (navigate/act/AI snapshot/role snapshot, element screenshots, PDF) require
 Playwright. If Playwright isn’t installed, those endpoints return a clear 501
-error. ARIA snapshots and basic screenshots still work for clawd-managed Chrome.
+error. ARIA snapshots and basic screenshots still work for openclaw-managed Chrome.
 For the Chrome extension relay driver, ARIA snapshots and screenshots require Playwright.
 
 If you see `Playwright is not available in this gateway build`, install the full
 Playwright package (not `playwright-core`) and restart the gateway, or reinstall
-Moltbot with browser support.
+OpenClaw with browser support.
 
 ## How it works (internal)
 
@@ -327,76 +327,76 @@ All commands accept `--browser-profile <name>` to target a specific profile.
 All commands also accept `--json` for machine-readable output (stable payloads).
 
 Basics:
-- `moltbot browser status`
-- `moltbot browser start`
-- `moltbot browser stop`
-- `moltbot browser tabs`
-- `moltbot browser tab`
-- `moltbot browser tab new`
-- `moltbot browser tab select 2`
-- `moltbot browser tab close 2`
-- `moltbot browser open https://example.com`
-- `moltbot browser focus abcd1234`
-- `moltbot browser close abcd1234`
+- `openclaw browser status`
+- `openclaw browser start`
+- `openclaw browser stop`
+- `openclaw browser tabs`
+- `openclaw browser tab`
+- `openclaw browser tab new`
+- `openclaw browser tab select 2`
+- `openclaw browser tab close 2`
+- `openclaw browser open https://example.com`
+- `openclaw browser focus abcd1234`
+- `openclaw browser close abcd1234`
 
 Inspection:
-- `moltbot browser screenshot`
-- `moltbot browser screenshot --full-page`
-- `moltbot browser screenshot --ref 12`
-- `moltbot browser screenshot --ref e12`
-- `moltbot browser snapshot`
-- `moltbot browser snapshot --format aria --limit 200`
-- `moltbot browser snapshot --interactive --compact --depth 6`
-- `moltbot browser snapshot --efficient`
-- `moltbot browser snapshot --labels`
-- `moltbot browser snapshot --selector "#main" --interactive`
-- `moltbot browser snapshot --frame "iframe#main" --interactive`
-- `moltbot browser console --level error`
-- `moltbot browser errors --clear`
-- `moltbot browser requests --filter api --clear`
-- `moltbot browser pdf`
-- `moltbot browser responsebody "**/api" --max-chars 5000`
+- `openclaw browser screenshot`
+- `openclaw browser screenshot --full-page`
+- `openclaw browser screenshot --ref 12`
+- `openclaw browser screenshot --ref e12`
+- `openclaw browser snapshot`
+- `openclaw browser snapshot --format aria --limit 200`
+- `openclaw browser snapshot --interactive --compact --depth 6`
+- `openclaw browser snapshot --efficient`
+- `openclaw browser snapshot --labels`
+- `openclaw browser snapshot --selector "#main" --interactive`
+- `openclaw browser snapshot --frame "iframe#main" --interactive`
+- `openclaw browser console --level error`
+- `openclaw browser errors --clear`
+- `openclaw browser requests --filter api --clear`
+- `openclaw browser pdf`
+- `openclaw browser responsebody "**/api" --max-chars 5000`
 
 Actions:
-- `moltbot browser navigate https://example.com`
-- `moltbot browser resize 1280 720`
-- `moltbot browser click 12 --double`
-- `moltbot browser click e12 --double`
-- `moltbot browser type 23 "hello" --submit`
-- `moltbot browser press Enter`
-- `moltbot browser hover 44`
-- `moltbot browser scrollintoview e12`
-- `moltbot browser drag 10 11`
-- `moltbot browser select 9 OptionA OptionB`
-- `moltbot browser download e12 /tmp/report.pdf`
-- `moltbot browser waitfordownload /tmp/report.pdf`
-- `moltbot browser upload /tmp/file.pdf`
-- `moltbot browser fill --fields '[{"ref":"1","type":"text","value":"Ada"}]'`
-- `moltbot browser dialog --accept`
-- `moltbot browser wait --text "Done"`
-- `moltbot browser wait "#main" --url "**/dash" --load networkidle --fn "window.ready===true"`
-- `moltbot browser evaluate --fn '(el) => el.textContent' --ref 7`
-- `moltbot browser highlight e12`
-- `moltbot browser trace start`
-- `moltbot browser trace stop`
+- `openclaw browser navigate https://example.com`
+- `openclaw browser resize 1280 720`
+- `openclaw browser click 12 --double`
+- `openclaw browser click e12 --double`
+- `openclaw browser type 23 "hello" --submit`
+- `openclaw browser press Enter`
+- `openclaw browser hover 44`
+- `openclaw browser scrollintoview e12`
+- `openclaw browser drag 10 11`
+- `openclaw browser select 9 OptionA OptionB`
+- `openclaw browser download e12 /tmp/report.pdf`
+- `openclaw browser waitfordownload /tmp/report.pdf`
+- `openclaw browser upload /tmp/file.pdf`
+- `openclaw browser fill --fields '[{"ref":"1","type":"text","value":"Ada"}]'`
+- `openclaw browser dialog --accept`
+- `openclaw browser wait --text "Done"`
+- `openclaw browser wait "#main" --url "**/dash" --load networkidle --fn "window.ready===true"`
+- `openclaw browser evaluate --fn '(el) => el.textContent' --ref 7`
+- `openclaw browser highlight e12`
+- `openclaw browser trace start`
+- `openclaw browser trace stop`
 
 State:
-- `moltbot browser cookies`
-- `moltbot browser cookies set session abc123 --url "https://example.com"`
-- `moltbot browser cookies clear`
-- `moltbot browser storage local get`
-- `moltbot browser storage local set theme dark`
-- `moltbot browser storage session clear`
-- `moltbot browser set offline on`
-- `moltbot browser set headers --json '{"X-Debug":"1"}'`
-- `moltbot browser set credentials user pass`
-- `moltbot browser set credentials --clear`
-- `moltbot browser set geo 37.7749 -122.4194 --origin "https://example.com"`
-- `moltbot browser set geo --clear`
-- `moltbot browser set media dark`
-- `moltbot browser set timezone America/New_York`
-- `moltbot browser set locale en-US`
-- `moltbot browser set device "iPhone 14"`
+- `openclaw browser cookies`
+- `openclaw browser cookies set session abc123 --url "https://example.com"`
+- `openclaw browser cookies clear`
+- `openclaw browser storage local get`
+- `openclaw browser storage local set theme dark`
+- `openclaw browser storage session clear`
+- `openclaw browser set offline on`
+- `openclaw browser set headers --json '{"X-Debug":"1"}'`
+- `openclaw browser set credentials user pass`
+- `openclaw browser set credentials --clear`
+- `openclaw browser set geo 37.7749 -122.4194 --origin "https://example.com"`
+- `openclaw browser set geo --clear`
+- `openclaw browser set media dark`
+- `openclaw browser set timezone America/New_York`
+- `openclaw browser set locale en-US`
+- `openclaw browser set device "iPhone 14"`
 
 Notes:
 - `upload` and `dialog` are **arming** calls; run them before the click/press
@@ -406,7 +406,7 @@ Notes:
   - `--format ai` (default when Playwright is installed): returns an AI snapshot with numeric refs (`aria-ref="<n>"`).
   - `--format aria`: returns the accessibility tree (no refs; inspection only).
   - `--efficient` (or `--mode efficient`): compact role snapshot preset (interactive + compact + depth + lower maxChars).
-  - Config default (tool/CLI only): set `browser.snapshotDefaults.mode: "efficient"` to use efficient snapshots when the caller does not pass a mode (see [Gateway configuration](/gateway/configuration#browser-clawd-managed-browser)).
+  - Config default (tool/CLI only): set `browser.snapshotDefaults.mode: "efficient"` to use efficient snapshots when the caller does not pass a mode (see [Gateway configuration](/gateway/configuration#browser-openclaw-managed-browser)).
   - Role snapshot options (`--interactive`, `--compact`, `--depth`, `--selector`) force a role-based snapshot with refs like `ref=e12`.
   - `--frame "<iframe selector>"` scopes role snapshots to an iframe (pairs with role refs like `e12`).
   - `--interactive` outputs a flat, easy-to-pick list of interactive elements (best for driving actions).
@@ -416,16 +416,16 @@ Notes:
 
 ## Snapshots and refs
 
-Moltbot supports two “snapshot” styles:
+OpenClaw supports two “snapshot” styles:
 
-- **AI snapshot (numeric refs)**: `moltbot browser snapshot` (default; `--format ai`)
+- **AI snapshot (numeric refs)**: `openclaw browser snapshot` (default; `--format ai`)
   - Output: a text snapshot that includes numeric refs.
-  - Actions: `moltbot browser click 12`, `moltbot browser type 23 "hello"`.
+  - Actions: `openclaw browser click 12`, `openclaw browser type 23 "hello"`.
   - Internally, the ref is resolved via Playwright’s `aria-ref`.
 
-- **Role snapshot (role refs like `e12`)**: `moltbot browser snapshot --interactive` (or `--compact`, `--depth`, `--selector`, `--frame`)
+- **Role snapshot (role refs like `e12`)**: `openclaw browser snapshot --interactive` (or `--compact`, `--depth`, `--selector`, `--frame`)
   - Output: a role-based list/tree with `[ref=e12]` (and optional `[nth=1]`).
-  - Actions: `moltbot browser click e12`, `moltbot browser highlight e12`.
+  - Actions: `openclaw browser click e12`, `openclaw browser highlight e12`.
   - Internally, the ref is resolved via `getByRole(...)` (plus `nth()` for duplicates).
   - Add `--labels` to include a viewport screenshot with overlayed `e12` labels.
 
@@ -438,18 +438,18 @@ Ref behavior:
 You can wait on more than just time/text:
 
 - Wait for URL (globs supported by Playwright):
-  - `moltbot browser wait --url "**/dash"`
+  - `openclaw browser wait --url "**/dash"`
 - Wait for load state:
-  - `moltbot browser wait --load networkidle`
+  - `openclaw browser wait --load networkidle`
 - Wait for a JS predicate:
-  - `moltbot browser wait --fn "window.ready===true"`
+  - `openclaw browser wait --fn "window.ready===true"`
 - Wait for a selector to become visible:
-  - `moltbot browser wait "#main"`
+  - `openclaw browser wait "#main"`
 
 These can be combined:
 
 ```bash
-moltbot browser wait "#main" \
+openclaw browser wait "#main" \
   --url "**/dash" \
   --load networkidle \
   --fn "window.ready===true" \
@@ -460,16 +460,16 @@ moltbot browser wait "#main" \
 
 When an action fails (e.g. “not visible”, “strict mode violation”, “covered”):
 
-1. `moltbot browser snapshot --interactive`
+1. `openclaw browser snapshot --interactive`
 2. Use `click <ref>` / `type <ref>` (prefer role refs in interactive mode)
-3. If it still fails: `moltbot browser highlight <ref>` to see what Playwright is targeting
+3. If it still fails: `openclaw browser highlight <ref>` to see what Playwright is targeting
 4. If the page behaves oddly:
-   - `moltbot browser errors --clear`
-   - `moltbot browser requests --filter api --clear`
+   - `openclaw browser errors --clear`
+   - `openclaw browser requests --filter api --clear`
 5. For deep debugging: record a trace:
-   - `moltbot browser trace start`
+   - `openclaw browser trace start`
    - reproduce the issue
-   - `moltbot browser trace stop` (prints `TRACE:<path>`)
+   - `openclaw browser trace stop` (prints `TRACE:<path>`)
 
 ## JSON output
 
@@ -478,10 +478,10 @@ When an action fails (e.g. “not visible”, “strict mode violation”, “co
 Examples:
 
 ```bash
-moltbot browser status --json
-moltbot browser snapshot --interactive --json
-moltbot browser requests --filter api --json
-moltbot browser cookies --json
+openclaw browser status --json
+openclaw browser snapshot --interactive --json
+openclaw browser requests --filter api --json
+openclaw browser cookies --json
 ```
 
 Role snapshots in JSON include `refs` plus a small `stats` block (lines/chars/refs/interactive) so tools can reason about payload size and density.
@@ -504,8 +504,8 @@ These are useful for “make the site behave like X” workflows:
 
 ## Security & privacy
 
-- The clawd browser profile may contain logged-in sessions; treat it as sensitive.
-- `browser act kind=evaluate` / `moltbot browser evaluate` and `wait --fn`
+- The openclaw browser profile may contain logged-in sessions; treat it as sensitive.
+- `browser act kind=evaluate` / `openclaw browser evaluate` and `wait --fn`
   execute arbitrary JavaScript in the page context. Prompt injection can steer
   this. Disable it with `browser.evaluateEnabled=false` if you do not need it.
 - For logins and anti-bot notes (X/Twitter, etc.), see [Browser login + X/Twitter posting](/tools/browser-login).
@@ -527,7 +527,7 @@ How it maps:
 - `browser act` uses the snapshot `ref` IDs to click/type/drag/select.
 - `browser screenshot` captures pixels (full page or element).
 - `browser` accepts:
-  - `profile` to choose a named browser profile (clawd, chrome, or remote CDP).
+  - `profile` to choose a named browser profile (openclaw, chrome, or remote CDP).
   - `target` (`sandbox` | `host` | `node`) to select where the browser lives.
   - In sandboxed sessions, `target: "host"` requires `agents.defaults.sandbox.browser.allowHostControl=true`.
   - If `target` is omitted: sandboxed sessions default to `sandbox`, non-sandbox sessions default to `host`.

package/docs/tools/chrome-extension.md

@@ -1,5 +1,5 @@
 ---
-summary: "Chrome extension: let Moltbot drive your existing Chrome tab"
+summary: "Chrome extension: let OpenClaw drive your existing Chrome tab"
 read_when:
   - You want the agent to drive an existing Chrome tab (toolbar button)
   - You need remote Gateway + local browser automation via Tailscale
@@ -8,7 +8,7 @@ read_when:
 
 # Chrome extension (browser relay)
 
-The Moltbot Chrome extension lets the agent control your **existing Chrome tabs** (your normal Chrome window) instead of launching a separate clawd-managed Chrome profile.
+The OpenClaw Chrome extension lets the agent control your **existing Chrome tabs** (your normal Chrome window) instead of launching a separate openclaw-managed Chrome profile.
 
 Attach/detach happens via a **single Chrome toolbar button**.
 
@@ -19,20 +19,20 @@ There are three parts:
 - **Local relay server** (loopback CDP): bridges between the control server and the extension (`http://127.0.0.1:18792` by default)
 - **Chrome MV3 extension**: attaches to the active tab using `chrome.debugger` and pipes CDP messages to the relay
 
-Moltbot then controls the attached tab through the normal `browser` tool surface (selecting the right profile).
+OpenClaw then controls the attached tab through the normal `browser` tool surface (selecting the right profile).
 
 ## Install / load (unpacked)
 
 1) Install the extension to a stable local path:
 
 ```bash
-moltbot browser extension install
+openclaw browser extension install
 ```
 
 2) Print the installed extension directory path:
 
 ```bash
-moltbot browser extension path
+openclaw browser extension path
 ```
 
 3) Chrome → `chrome://extensions`
@@ -43,24 +43,24 @@ moltbot browser extension path
 
 ## Updates (no build step)
 
-The extension ships inside the Moltbot release (npm package) as static files. There is no separate “build” step.
+The extension ships inside the OpenClaw release (npm package) as static files. There is no separate “build” step.
 
-After upgrading Moltbot:
-- Re-run `moltbot browser extension install` to refresh the installed files under your Moltbot state directory.
+After upgrading OpenClaw:
+- Re-run `openclaw browser extension install` to refresh the installed files under your OpenClaw state directory.
 - Chrome → `chrome://extensions` → click “Reload” on the extension.
 
 ## Use it (no extra config)
 
-Moltbot ships with a built-in browser profile named `chrome` that targets the extension relay on the default port.
+OpenClaw ships with a built-in browser profile named `chrome` that targets the extension relay on the default port.
 
 Use it:
-- CLI: `moltbot browser --browser-profile chrome tabs`
+- CLI: `openclaw browser --browser-profile chrome tabs`
 - Agent tool: `browser` with `profile="chrome"`
 
 If you want a different name or a different relay port, create your own profile:
 
 ```bash
-moltbot browser create-profile \
+openclaw browser create-profile \
   --name my-chrome \
   --driver extension \
   --cdp-url http://127.0.0.1:18792 \
@@ -69,7 +69,7 @@ moltbot browser create-profile \
 
 ## Attach / detach (toolbar button)
 
-- Open the tab you want Moltbot to control.
+- Open the tab you want OpenClaw to control.
 - Click the extension icon.
   - Badge shows `ON` when attached.
 - Click again to detach.
@@ -82,7 +82,7 @@ moltbot browser create-profile \
 
 ## Badge + common errors
 
-- `ON`: attached; Moltbot can drive that tab.
+- `ON`: attached; OpenClaw can drive that tab.
 - `…`: connecting to the local relay.
 - `!`: relay not reachable (most common: browser relay server isn’t running on this machine).
 
@@ -131,7 +131,7 @@ Options:
 
 Then ensure the tool isn’t denied by tool policy, and (if needed) call `browser` with `target="host"`.
 
-Debugging: `moltbot sandbox explain`
+Debugging: `openclaw sandbox explain`
 
 ## Remote access tips
 
@@ -140,9 +140,9 @@ Debugging: `moltbot sandbox explain`
 
 ## How “extension path” works
 
-`moltbot browser extension path` prints the **installed** on-disk directory containing the extension files.
+`openclaw browser extension path` prints the **installed** on-disk directory containing the extension files.
 
-The CLI intentionally does **not** print a `node_modules` path. Always run `moltbot browser extension install` first to copy the extension to a stable location under your Moltbot state directory.
+The CLI intentionally does **not** print a `node_modules` path. Always run `openclaw browser extension install` first to copy the extension to a stable location under your OpenClaw state directory.
 
 If you move or delete that install directory, Chrome will mark the extension as broken until you reload it from a valid path.
 
@@ -154,7 +154,7 @@ This is powerful and risky. Treat it like giving the model “hands on your brow
   - click/type/navigate in that tab
   - read page content
   - access whatever the tab’s logged-in session can access
-- **This is not isolated** like the dedicated clawd-managed profile.
+- **This is not isolated** like the dedicated openclaw-managed profile.
   - If you attach to your daily-driver profile/tab, you’re granting access to that account state.
 
 Recommendations:

package/docs/tools/clawdhub.md

@@ -8,13 +8,13 @@ read_when:
 
 # ClawdHub
 
-ClawdHub is the **public skill registry for Moltbot**. It is a free service: all skills are public, open, and visible to everyone for sharing and reuse. A skill is just a folder with a `SKILL.md` file (plus supporting text files). You can browse skills in the web app or use the CLI to search, install, update, and publish skills.
+ClawdHub is the **public skill registry for OpenClaw**. It is a free service: all skills are public, open, and visible to everyone for sharing and reuse. A skill is just a folder with a `SKILL.md` file (plus supporting text files). You can browse skills in the web app or use the CLI to search, install, update, and publish skills.
 
 Site: [clawdhub.com](https://clawdhub.com)
 
 ## Who this is for (beginner-friendly)
 
-If you want to add new capabilities to your Moltbot agent, ClawdHub is the easiest way to find and install skills. You do not need to know how the backend works. You can:
+If you want to add new capabilities to your OpenClaw agent, ClawdHub is the easiest way to find and install skills. You do not need to know how the backend works. You can:
 
 - Search for skills by plain language.
 - Install a skill into your workspace.
@@ -28,7 +28,7 @@ If you want to add new capabilities to your Moltbot agent, ClawdHub is the easie
    - `clawdhub search "calendar"`
 3) Install a skill:
    - `clawdhub install <skill-slug>`
-4) Start a new Moltbot session so it picks up the new skill.
+4) Start a new OpenClaw session so it picks up the new skill.
 
 ## Install the CLI
 
@@ -42,9 +42,9 @@ npm i -g clawdhub
 pnpm add -g clawdhub
 ```
 
-## How it fits into Moltbot
+## How it fits into OpenClaw
 
-By default, the CLI installs skills into `./skills` under your current working directory. If a Moltbot workspace is configured, `clawdhub` falls back to that workspace unless you override `--workdir` (or `CLAWDHUB_WORKDIR`). Moltbot loads workspace skills from `<workspace>/skills` and will pick them up in the **next** session. If you already use `~/.clawdbot/skills` or bundled skills, workspace skills take precedence.
+By default, the CLI installs skills into `./skills` under your current working directory. If a OpenClaw workspace is configured, `clawdhub` falls back to that workspace unless you override `--workdir` (or `CLAWDHUB_WORKDIR`). OpenClaw loads workspace skills from `<workspace>/skills` and will pick them up in the **next** session. If you already use `~/.openclaw/skills` or bundled skills, workspace skills take precedence.
 
 For more detail on how skills are loaded, shared, and gated, see
 [Skills](/tools/skills).
@@ -63,7 +63,7 @@ For more detail on how skills are loaded, shared, and gated, see
 
 Global options (apply to all commands):
 
-- `--workdir <dir>`: Working directory (default: current dir; falls back to Moltbot workspace).
+- `--workdir <dir>`: Working directory (default: current dir; falls back to OpenClaw workspace).
 - `--dir <dir>`: Skills directory, relative to workdir (default: `skills`).
 - `--site <url>`: Site base URL (browser login).
 - `--registry <url>`: Registry API base URL.
@@ -177,7 +177,7 @@ Updates compare the local skill contents to registry versions using a content ha
 
 ### Sync scanning and fallback roots
 
-`clawdhub sync` scans your current workdir first. If no skills are found, it falls back to known legacy locations (for example `~/moltbot/skills` and `~/.clawdbot/skills`). This is designed to find older skill installs without extra flags.
+`clawdhub sync` scans your current workdir first. If no skills are found, it falls back to known legacy locations (for example `~/openclaw/skills` and `~/.openclaw/skills`). This is designed to find older skill installs without extra flags.
 
 ### Storage and lockfile