@gguf/pigbot 0.0.1 → 0.0.2

package/docs/providers/openrouter.md

@@ -1,8 +1,8 @@
 ---
-summary: "Use OpenRouter's unified API to access many models in Pigbot"
+summary: "Use OpenRouter's unified API to access many models in Moltbot"
 read_when:
   - You want a single API key for many LLMs
-  - You want to run models via OpenRouter in Pigbot
+  - You want to run models via OpenRouter in Moltbot
 ---
 # OpenRouter
 
@@ -12,7 +12,7 @@ endpoint and API key. It is OpenAI-compatible, so most OpenAI SDKs work by switc
 ## CLI setup
 
 ```bash
-pigbot onboard --auth-choice apiKey --token-provider openrouter --token "$OPENROUTER_API_KEY"
+moltbot onboard --auth-choice apiKey --token-provider openrouter --token "$OPENROUTER_API_KEY"
 ```
 
 ## Config snippet

package/docs/providers/qwen.md

@@ -1,7 +1,7 @@
 ---
-summary: "Use Qwen OAuth (free tier) in Pigbot"
+summary: "Use Qwen OAuth (free tier) in Moltbot"
 read_when:
-  - You want to use Qwen with Pigbot
+  - You want to use Qwen with Moltbot
   - You want free-tier OAuth access to Qwen Coder
 ---
 # Qwen
@@ -12,7 +12,7 @@ Qwen provides a free-tier OAuth flow for Qwen Coder and Qwen Vision models
 ## Enable the plugin
 
 ```bash
-pigbot plugins enable qwen-portal-auth
+moltbot plugins enable qwen-portal-auth
 ```
 
 Restart the Gateway after enabling.
@@ -20,7 +20,7 @@ Restart the Gateway after enabling.
 ## Authenticate
 
 ```bash
-pigbot models auth login --provider qwen-portal --set-default
+moltbot models auth login --provider qwen-portal --set-default
 ```
 
 This runs the Qwen device-code OAuth flow and writes a provider entry to your
@@ -34,12 +34,12 @@ This runs the Qwen device-code OAuth flow and writes a provider entry to your
 Switch models with:
 
 ```bash
-pigbot models set qwen-portal/coder-model
+moltbot models set qwen-portal/coder-model
 ```
 
 ## Reuse Qwen Code CLI login
 
-If you already logged in with the Qwen Code CLI, Pigbot will sync credentials
+If you already logged in with the Qwen Code CLI, Moltbot will sync credentials
 from `~/.qwen/oauth_creds.json` when it loads the auth store. You still need a
 `models.providers.qwen-portal` entry (use the login command above to create one).
 

package/docs/providers/synthetic.md

@@ -1,12 +1,12 @@
 ---
-summary: "Use Synthetic's Anthropic-compatible API in Pigbot"
+summary: "Use Synthetic's Anthropic-compatible API in Moltbot"
 read_when:
   - You want to use Synthetic as a model provider
   - You need a Synthetic API key or base URL setup
 ---
 # Synthetic
 
-Synthetic exposes Anthropic-compatible endpoints. Pigbot registers it as the
+Synthetic exposes Anthropic-compatible endpoints. Moltbot registers it as the
 `synthetic` provider and uses the Anthropic Messages API.
 
 ## Quick setup
@@ -15,7 +15,7 @@ Synthetic exposes Anthropic-compatible endpoints. Pigbot registers it as the
 2) Run onboarding:
 
 ```bash
-pigbot onboard --auth-choice synthetic-api-key
+moltbot onboard --auth-choice synthetic-api-key
 ```
 
 The default model is set to:
@@ -59,7 +59,7 @@ synthetic/hf:MiniMaxAI/MiniMax-M2.1
 }
 ```
 
-Note: Pigbot's Anthropic client appends `/v1` to the base URL, so use
+Note: Moltbot's Anthropic client appends `/v1` to the base URL, so use
 `https://api.synthetic.new/anthropic` (not `/anthropic/v1`). If Synthetic changes
 its base URL, override `models.providers.synthetic.baseUrl`.
 

package/docs/providers/venice.md

@@ -1,7 +1,7 @@
 ---
-summary: "Use Venice AI privacy-focused models in Pigbot"
+summary: "Use Venice AI privacy-focused models in Moltbot"
 read_when:
-  - You want privacy-focused inference in Pigbot
+  - You want privacy-focused inference in Moltbot
   - You want Venice AI setup guidance
 ---
 # Venice AI (Venius highlight)
@@ -10,7 +10,7 @@ read_when:
 
 Venice AI provides privacy-focused AI inference with support for uncensored models and access to major proprietary models through their anonymized proxy. All inference is private by default—no training on your data, no logging.
 
-## Why Venice in Pigbot
+## Why Venice in Moltbot
 
 - **Private inference** for open-source models (no logging).
 - **Uncensored models** when you need them.
@@ -45,7 +45,7 @@ Venice offers two privacy levels — understanding this is key to choosing your
 2. Go to **Settings → API Keys → Create new key**
 3. Copy your API key (format: `vapi_xxxxxxxxxxxx`)
 
-### 2. Configure Pigbot
+### 2. Configure Moltbot
 
 **Option A: Environment Variable**
 
@@ -56,7 +56,7 @@ export VENICE_API_KEY="vapi_xxxxxxxxxxxx"
 **Option B: Interactive Setup (Recommended)**
 
 ```bash
-pigbot onboard --auth-choice venice-api-key
+moltbot onboard --auth-choice venice-api-key
 ```
 
 This will:
@@ -68,7 +68,7 @@ This will:
 **Option C: Non-interactive**
 
 ```bash
-pigbot onboard --non-interactive \
+moltbot onboard --non-interactive \
   --auth-choice venice-api-key \
   --venice-api-key "vapi_xxxxxxxxxxxx"
 ```
@@ -76,12 +76,12 @@ pigbot onboard --non-interactive \
 ### 3. Verify Setup
 
 ```bash
-pigbot chat --model venice/llama-3.3-70b "Hello, are you working?"
+moltbot chat --model venice/llama-3.3-70b "Hello, are you working?"
 ```
 
 ## Model Selection
 
-After setup, Pigbot shows all available Venice models. Pick based on your needs:
+After setup, Moltbot shows all available Venice models. Pick based on your needs:
 
 - **Default (our pick)**: `venice/llama-3.3-70b` for private, balanced performance.
 - **Best overall quality**: `venice/claude-opus-45` for hard jobs (Opus remains the strongest).
@@ -91,19 +91,19 @@ After setup, Pigbot shows all available Venice models. Pick based on your needs:
 Change your default model anytime:
 
 ```bash
-pigbot models set venice/claude-opus-45
-pigbot models set venice/llama-3.3-70b
+moltbot models set venice/claude-opus-45
+moltbot models set venice/llama-3.3-70b
 ```
 
 List all available models:
 
 ```bash
-pigbot models list | grep venice
+moltbot models list | grep venice
 ```
 
-## Configure via `pigbot configure`
+## Configure via `moltbot configure`
 
-1. Run `pigbot configure`
+1. Run `moltbot configure`
 2. Select **Model/auth**
 3. Choose **Venice AI**
 
@@ -159,7 +159,7 @@ pigbot models list | grep venice
 
 ## Model Discovery
 
-Pigbot automatically discovers models from the Venice API when `VENICE_API_KEY` is set. If the API is unreachable, it falls back to a static catalog.
+Moltbot automatically discovers models from the Venice API when `VENICE_API_KEY` is set. If the API is unreachable, it falls back to a static catalog.
 
 The `/models` endpoint is public (no auth needed for listing), but inference requires a valid API key.
 
@@ -192,19 +192,19 @@ Venice uses a credit-based system. Check [venice.ai/pricing](https://venice.ai/p
 
 ```bash
 # Use default private model
-pigbot chat --model venice/llama-3.3-70b
+moltbot chat --model venice/llama-3.3-70b
 
 # Use Claude via Venice (anonymized)
-pigbot chat --model venice/claude-opus-45
+moltbot chat --model venice/claude-opus-45
 
 # Use uncensored model
-pigbot chat --model venice/venice-uncensored
+moltbot chat --model venice/venice-uncensored
 
 # Use vision model with image
-pigbot chat --model venice/qwen3-vl-235b-a22b
+moltbot chat --model venice/qwen3-vl-235b-a22b
 
 # Use coding model
-pigbot chat --model venice/qwen3-coder-480b-a35b-instruct
+moltbot chat --model venice/qwen3-coder-480b-a35b-instruct
 ```
 
 ## Troubleshooting
@@ -213,14 +213,14 @@ pigbot chat --model venice/qwen3-coder-480b-a35b-instruct
 
 ```bash
 echo $VENICE_API_KEY
-pigbot models list | grep venice
+moltbot models list | grep venice
 ```
 
 Ensure the key starts with `vapi_`.
 
 ### Model not available
 
-The Venice model catalog updates dynamically. Run `pigbot models list` to see currently available models. Some models may be temporarily offline.
+The Venice model catalog updates dynamically. Run `moltbot models list` to see currently available models. Some models may be temporarily offline.
 
 ### Connection issues
 

package/docs/providers/vercel-ai-gateway.md

@@ -1,7 +1,8 @@
 ---
+title: "Vercel AI Gateway"
 summary: "Vercel AI Gateway setup (auth + model selection)"
 read_when:
-  - You want to use Vercel AI Gateway with Pigbot
+  - You want to use Vercel AI Gateway with Moltbot
   - You need the API key env var or CLI auth choice
 ---
 # Vercel AI Gateway
@@ -18,7 +19,7 @@ The [Vercel AI Gateway](https://vercel.com/ai-gateway) provides a unified API to
 1) Set the API key (recommended: store it for the Gateway):
 
 ```bash
-pigbot onboard --auth-choice ai-gateway-api-key
+moltbot onboard --auth-choice ai-gateway-api-key
 ```
 
 2) Set a default model:
@@ -36,7 +37,7 @@ pigbot onboard --auth-choice ai-gateway-api-key
 ## Non-interactive example
 
 ```bash
-pigbot onboard --non-interactive \
+moltbot onboard --non-interactive \
   --mode local \
   --auth-choice ai-gateway-api-key \
   --ai-gateway-api-key "$AI_GATEWAY_API_KEY"
@@ -45,5 +46,5 @@ pigbot onboard --non-interactive \
 ## Environment note
 
 If the Gateway runs as a daemon (launchd/systemd), make sure `AI_GATEWAY_API_KEY`
-is available to that process (for example, in `~/.pigbot/.env` or via
+is available to that process (for example, in `~/.clawdbot/.env` or via
 `env.shellEnv`).

package/docs/providers/zai.md

@@ -1,21 +1,21 @@
 ---
-summary: "Use Z.AI (GLM models) with Pigbot"
+summary: "Use Z.AI (GLM models) with Moltbot"
 read_when:
-  - You want Z.AI / GLM models in Pigbot
+  - You want Z.AI / GLM models in Moltbot
   - You need a simple ZAI_API_KEY setup
 ---
 # Z.AI
 
 Z.AI is the API platform for **GLM** models. It provides REST APIs for GLM and uses API keys
-for authentication. Create your API key in the Z.AI console. Pigbot uses the `zai` provider
+for authentication. Create your API key in the Z.AI console. Moltbot uses the `zai` provider
 with a Z.AI API key.
 
 ## CLI setup
 
 ```bash
-pigbot onboard --auth-choice zai-api-key
+moltbot onboard --auth-choice zai-api-key
 # or non-interactive
-pigbot onboard --zai-api-key "$ZAI_API_KEY"
+moltbot onboard --zai-api-key "$ZAI_API_KEY"
 ```
 
 ## Config snippet

package/docs/railway.mdx

@@ -2,7 +2,7 @@
 title: Deploy on Railway
 ---
 
-Deploy Clawdbot on Railway with a one-click template and finish setup in your browser.
+Deploy Moltbot on Railway with a one-click template and finish setup in your browser.
 This is the easiest “no terminal on the server” path: Railway runs the Gateway for you,
 and you configure everything via the `/setup` web wizard.
 
@@ -16,7 +16,7 @@ and you configure everything via the `/setup` web wizard.
 
 ## One-click deploy
 
-<a href="https://railway.com/deploy/clawdbot-railway-template" target="_blank" rel="noreferrer">Deploy on Railway</a>
+<a href="https://railway.com/deploy/moltbot-railway-template" target="_blank" rel="noreferrer">Deploy on Railway</a>
 
 After deploy, find your public URL in **Railway → your service → Settings → Domains**.
 
@@ -27,11 +27,11 @@ Railway will either:
 Then open:
 
 - `https://<your-railway-domain>/setup` — setup wizard (password protected)
-- `https://<your-railway-domain>/clawdbot` — Control UI
+- `https://<your-railway-domain>/moltbot` — Control UI
 
 ## What you get
 
-- Hosted Clawdbot Gateway + Control UI
+- Hosted Moltbot Gateway + Control UI
 - Web setup wizard at `/setup` (no terminal commands)
 - Persistent storage via Railway Volume (`/data`) so config/credentials/workspace survive redeploys
 - Backup export at `/setup/export` to migrate off Railway later
@@ -55,6 +55,7 @@ Attach a volume mounted at:
 Set these variables on the service:
 
 - `SETUP_PASSWORD` (required)
+- `PORT=8080` (required — must match the port in Public Networking)
 - `CLAWDBOT_STATE_DIR=/data/.clawdbot` (recommended)
 - `CLAWDBOT_WORKSPACE_DIR=/data/workspace` (recommended)
 - `CLAWDBOT_GATEWAY_TOKEN` (recommended; treat as an admin secret)
@@ -82,8 +83,9 @@ If Telegram DMs are set to pairing, the setup wizard can approve the pairing cod
 1) Go to https://discord.com/developers/applications
 2) **New Application** → choose a name
 3) **Bot** → **Add Bot**
-4) Copy the **Bot Token** and paste into `/setup`
-5) Invite the bot to your server (OAuth2 URL Generator; scopes: `bot`, `applications.commands`)
+4) **Enable MESSAGE CONTENT INTENT** under Bot → Privileged Gateway Intents (required or the bot will crash on startup)
+5) Copy the **Bot Token** and paste into `/setup`
+6) Invite the bot to your server (OAuth2 URL Generator; scopes: `bot`, `applications.commands`)
 
 ## Backups & migration
 
@@ -91,4 +93,4 @@ Download a backup at:
 
 - `https://<your-railway-domain>/setup/export`
 
-This exports your Clawdbot state + workspace so you can migrate to another host without losing config or memory.
+This exports your Moltbot state + workspace so you can migrate to another host without losing config or memory.

package/docs/refactor/exec-host.md

@@ -25,11 +25,11 @@ read_when:
 - **Config keys:** `exec.host` + `exec.security` (per-agent override allowed).
 - **Elevation:** keep `/elevated` as an alias for gateway full access.
 - **Ask default:** `on-miss`.
-- **Approvals store:** `~/.pigbot/exec-approvals.json` (JSON, no legacy migration).
+- **Approvals store:** `~/.clawdbot/exec-approvals.json` (JSON, no legacy migration).
 - **Runner:** headless system service; UI app hosts a Unix socket for approvals.
 - **Node identity:** use existing `nodeId`.
 - **Socket auth:** Unix socket + token (cross-platform); split later if needed.
-- **Node host state:** `~/.pigbot/node.json` (node id + pairing token).
+- **Node host state:** `~/.clawdbot/node.json` (node id + pairing token).
 - **macOS exec host:** run `system.run` inside the macOS app; node host service forwards requests over local IPC.
 - **No XPC helper:** stick to Unix socket + token + peer checks.
 
@@ -87,7 +87,7 @@ Ask is **independent** of allowlist; allowlist can be used with `always` or `on-
 - `/elevated off` = restore previous exec settings for the agent session.
 
 ## Approvals store (JSON)
-Path: `~/.pigbot/exec-approvals.json`
+Path: `~/.clawdbot/exec-approvals.json`
 
 Purpose:
 - Local policy + allowlists for the **execution host** (gateway or node runner).
@@ -99,7 +99,7 @@ Proposed schema (v1):
 {
   "version": 1,
   "socket": {
-    "path": "~/.pigbot/exec-approvals.sock",
+    "path": "~/.clawdbot/exec-approvals.sock",
     "token": "base64-opaque-token"
   },
   "defaults": {
@@ -141,7 +141,7 @@ Notes:
 
 ## UI integration (macOS app)
 ### IPC
-- Unix socket at `~/.pigbot/exec-approvals.sock` (0600).
+- Unix socket at `~/.clawdbot/exec-approvals.sock` (0600).
 - Token stored in `exec-approvals.json` (0600).
 - Peer checks: same-UID only.
 - Challenge/response: nonce + HMAC(token, request-hash) to prevent replay.

package/docs/refactor/plugin-sdk.md

@@ -28,12 +28,12 @@ Contents (examples):
 - Docs link helper: `formatDocsLink`.
 
 Delivery:
-- Publish as `@pigbot/plugin-sdk` (or export from core under `pigbot/plugin-sdk`).
+- Publish as `@clawdbot/plugin-sdk` (or export from core under `clawdbot/plugin-sdk`).
 - Semver with explicit stability guarantees.
 
 ### 2) Plugin Runtime (execution surface, injected)
 Scope: everything that touches core runtime behavior.
-Accessed via `PigbotPluginApi.runtime` so plugins never import `src/**`.
+Accessed via `MoltbotPluginApi.runtime` so plugins never import `src/**`.
 
 Proposed surface (minimal but complete):
 ```ts
@@ -41,8 +41,8 @@ export type PluginRuntime = {
   channel: {
     text: {
       chunkMarkdownText(text: string, limit: number): string[];
-      resolveTextChunkLimit(cfg: PigbotConfig, channel: string, accountId?: string): number;
-      hasControlCommand(text: string, cfg: PigbotConfig): boolean;
+      resolveTextChunkLimit(cfg: MoltbotConfig, channel: string, accountId?: string): number;
+      hasControlCommand(text: string, cfg: MoltbotConfig): boolean;
     };
     reply: {
       dispatchReplyWithBufferedBlockDispatcher(params: {
@@ -83,18 +83,18 @@ export type PluginRuntime = {
       ): Promise<{ path: string; contentType?: string }>;
     };
     mentions: {
-      buildMentionRegexes(cfg: PigbotConfig, agentId?: string): RegExp[];
+      buildMentionRegexes(cfg: MoltbotConfig, agentId?: string): RegExp[];
       matchesMentionPatterns(text: string, regexes: RegExp[]): boolean;
     };
     groups: {
-      resolveGroupPolicy(cfg: PigbotConfig, channel: string, accountId: string, groupId: string): {
+      resolveGroupPolicy(cfg: MoltbotConfig, channel: string, accountId: string, groupId: string): {
         allowlistEnabled: boolean;
         allowed: boolean;
         groupConfig?: unknown;
         defaultConfig?: unknown;
       };
       resolveRequireMention(
-        cfg: PigbotConfig,
+        cfg: MoltbotConfig,
         channel: string,
         accountId: string,
         groupId: string,
@@ -109,7 +109,7 @@ export type PluginRuntime = {
         onFlush: (entries: T[]) => Promise<void>;
         onError?: (err: unknown) => void;
       }): { push: (v: T) => void; flush: () => Promise<void> };
-      resolveInboundDebounceMs(cfg: PigbotConfig, channel: string): number;
+      resolveInboundDebounceMs(cfg: MoltbotConfig, channel: string): number;
     };
     commands: {
       resolveCommandAuthorizedFromAuthorizers(params: {
@@ -123,7 +123,7 @@ export type PluginRuntime = {
     getChildLogger(name: string): PluginLogger;
   };
   state: {
-    resolveStateDir(cfg: PigbotConfig): string;
+    resolveStateDir(cfg: MoltbotConfig): string;
   };
 };
 ```
@@ -136,8 +136,8 @@ Notes:
 ## Migration plan (phased, safe)
 
 ### Phase 0: scaffolding
-- Introduce `@pigbot/plugin-sdk`.
-- Add `api.runtime` to `PigbotPluginApi` with the surface above.
+- Introduce `@clawdbot/plugin-sdk`.
+- Add `api.runtime` to `MoltbotPluginApi` with the surface above.
 - Maintain existing imports during a transition window (deprecation warnings).
 
 ### Phase 1: bridge cleanup (low risk)
@@ -165,7 +165,7 @@ Notes:
 ## Compatibility and versioning
 - SDK: semver, published, documented changes.
 - Runtime: versioned per core release. Add `api.runtime.version`.
-- Plugins declare a required runtime range (e.g., `pigbotRuntime: ">=2026.2.0"`).
+- Plugins declare a required runtime range (e.g., `moltbotRuntime: ">=2026.2.0"`).
 
 ## Testing strategy
 - Adapter-level unit tests (runtime functions exercised with real core implementation).

package/docs/refactor/strict-config.md

@@ -23,12 +23,12 @@ read_when:
 - `plugins.entries.<id>.config` must be validated by the plugin’s schema.
   - If a plugin lacks a schema, **reject plugin load** and surface a clear error.
 - Unknown `channels.<id>` keys are errors unless a plugin manifest declares the channel id.
-- Plugin manifests (`pigbot.plugin.json`) are required for all plugins.
+- Plugin manifests (`moltbot.plugin.json`) are required for all plugins.
 
 ## Plugin schema enforcement
 - Each plugin provides a strict JSON Schema for its config (inline in the manifest).
 - Plugin load flow:
-  1) Resolve plugin manifest + schema (`pigbot.plugin.json`).
+  1) Resolve plugin manifest + schema (`moltbot.plugin.json`).
   2) Validate config against the schema.
   3) If missing schema or invalid config: block plugin load, record error.
 - Error message includes:
@@ -41,22 +41,22 @@ read_when:
 - Doctor runs **every time** config is loaded (dry-run by default).
 - If config invalid:
   - Print a summary + actionable errors.
-  - Instruct: `pigbot doctor --fix`.
-- `pigbot doctor --fix`:
+  - Instruct: `moltbot doctor --fix`.
+- `moltbot doctor --fix`:
   - Applies migrations.
   - Removes unknown keys.
   - Writes updated config.
 
 ## Command gating (when config is invalid)
 Allowed (diagnostic-only):
-- `pigbot doctor`
-- `pigbot logs`
-- `pigbot health`
-- `pigbot help`
-- `pigbot status`
-- `pigbot gateway status`
+- `moltbot doctor`
+- `moltbot logs`
+- `moltbot health`
+- `moltbot help`
+- `moltbot status`
+- `moltbot gateway status`
 
-Everything else must hard-fail with: “Config invalid. Run `pigbot doctor --fix`.”
+Everything else must hard-fail with: “Config invalid. Run `moltbot doctor --fix`.”
 
 ## Error UX format
 - Single summary header.

package/docs/reference/AGENTS.default.md

@@ -1,14 +1,14 @@
 ---
-summary: "Default Pigbot agent instructions and skills roster for the personal assistant setup"
+summary: "Default Moltbot agent instructions and skills roster for the personal assistant setup"
 read_when:
-  - Starting a new Pigbot agent session
+  - Starting a new Moltbot agent session
   - Enabling or auditing default skills
 ---
-# AGENTS.md — Pigbot Personal Assistant (default)
+# AGENTS.md — Moltbot Personal Assistant (default)
 
 ## First run (recommended)
 
-Pigbot uses a dedicated workspace directory for the agent. Default: `~/clawd` (configurable via `agents.defaults.workspace`).
+Moltbot uses a dedicated workspace directory for the agent. Default: `~/clawd` (configurable via `agents.defaults.workspace`).
 
 1) Create the workspace (if it doesn’t already exist):
 
@@ -78,9 +78,9 @@ git commit -m "Add Clawd workspace"
 # Optional: add a private remote + push
 ```
 
-## What Pigbot Does
+## What Moltbot Does
 - Runs WhatsApp gateway + Pi coding agent so the assistant can read/write chats, fetch context, and run skills via the host Mac.
-- macOS app manages permissions (screen recording, notifications, microphone) and exposes the `pigbot` CLI via its bundled binary.
+- macOS app manages permissions (screen recording, notifications, microphone) and exposes the `moltbot` CLI via its bundled binary.
 - Direct chats collapse into the agent's `main` session by default; groups stay isolated as `agent:<agentId>:<channel>:group:<id>` (rooms/channels: `agent:<agentId>:<channel>:channel:<id>`); heartbeats keep background tasks alive.
 
 ## Core Skills (enable in Settings → Skills)
@@ -104,10 +104,10 @@ git commit -m "Add Clawd workspace"
 - **agent-tools** — Utility toolkit for automations and helper scripts.
 
 ## Usage Notes
-- Prefer the `pigbot` CLI for scripting; mac app handles permissions.
+- Prefer the `moltbot` CLI for scripting; mac app handles permissions.
 - Run installs from the Skills tab; it hides the button if a binary is already present.
 - Keep heartbeats enabled so the assistant can schedule reminders, monitor inboxes, and trigger camera captures.
 - Canvas UI runs full-screen with native overlays. Avoid placing critical controls in the top-left/top-right/bottom edges; add explicit gutters in the layout and don’t rely on safe-area insets.
-- For browser-driven verification, use `pigbot browser` (tabs/status/screenshot) with the clawd-managed Chrome profile.
-- For DOM inspection, use `pigbot browser eval|query|dom|snapshot` (and `--json`/`--out` when you need machine output).
-- For interactions, use `pigbot browser click|type|hover|drag|select|upload|press|wait|navigate|back|evaluate|run` (click/type require snapshot refs; use `evaluate` for CSS selectors).
+- For browser-driven verification, use `moltbot browser` (tabs/status/screenshot) with the clawd-managed Chrome profile.
+- For DOM inspection, use `moltbot browser eval|query|dom|snapshot` (and `--json`/`--out` when you need machine output).
+- For interactions, use `moltbot browser click|type|hover|drag|select|upload|press|wait|navigate|back|evaluate|run` (click/type require snapshot refs; use `evaluate` for CSS selectors).