@gguf/pigbot 0.0.1 → 0.0.3

package/docs/cli/acp.md

@@ -7,7 +7,7 @@ read_when:
 
 # acp
 
-Run the ACP (Agent Client Protocol) bridge that talks to a Pigbot Gateway.
+Run the ACP (Agent Client Protocol) bridge that talks to a Moltbot Gateway.
 
 This command speaks ACP over stdio for IDEs and forwards prompts to the Gateway
 over WebSocket. It keeps ACP sessions mapped to Gateway session keys.
@@ -15,19 +15,19 @@ over WebSocket. It keeps ACP sessions mapped to Gateway session keys.
 ## Usage
 
 ```bash
-pigbot acp
+moltbot acp
 
 # Remote Gateway
-pigbot acp --url wss://gateway-host:18789 --token <token>
+moltbot acp --url wss://gateway-host:18789 --token <token>
 
 # Attach to an existing session key
-pigbot acp --session agent:main:main
+moltbot acp --session agent:main:main
 
 # Attach by label (must already exist)
-pigbot acp --session-label "support inbox"
+moltbot acp --session-label "support inbox"
 
 # Reset the session key before the first prompt
-pigbot acp --session agent:main:main --reset-session
+moltbot acp --session agent:main:main --reset-session
 ```
 
 ## ACP client (debug)
@@ -36,35 +36,35 @@ Use the built-in ACP client to sanity-check the bridge without an IDE.
 It spawns the ACP bridge and lets you type prompts interactively.
 
 ```bash
-pigbot acp client
+moltbot acp client
 
 # Point the spawned bridge at a remote Gateway
-pigbot acp client --server-args --url wss://gateway-host:18789 --token <token>
+moltbot acp client --server-args --url wss://gateway-host:18789 --token <token>
 
-# Override the server command (default: pigbot)
-pigbot acp client --server "node" --server-args dist/entry.js acp --url ws://127.0.0.1:19001
+# Override the server command (default: moltbot)
+moltbot acp client --server "node" --server-args dist/entry.js acp --url ws://127.0.0.1:19001
 ```
 
 ## How to use this
 
 Use ACP when an IDE (or other client) speaks Agent Client Protocol and you want
-it to drive a Pigbot Gateway session.
+it to drive a Moltbot Gateway session.
 
 1. Ensure the Gateway is running (local or remote).
 2. Configure the Gateway target (config or flags).
-3. Point your IDE to run `pigbot acp` over stdio.
+3. Point your IDE to run `moltbot acp` over stdio.
 
 Example config (persisted):
 
 ```bash
-pigbot config set gateway.remote.url wss://gateway-host:18789
-pigbot config set gateway.remote.token <token>
+moltbot config set gateway.remote.url wss://gateway-host:18789
+moltbot config set gateway.remote.token <token>
 ```
 
 Example direct run (no config write):
 
 ```bash
-pigbot acp --url wss://gateway-host:18789 --token <token>
+moltbot acp --url wss://gateway-host:18789 --token <token>
 ```
 
 ## Selecting agents
@@ -74,9 +74,9 @@ ACP does not pick agents directly. It routes by the Gateway session key.
 Use agent-scoped session keys to target a specific agent:
 
 ```bash
-pigbot acp --session agent:main:main
-pigbot acp --session agent:design:main
-pigbot acp --session agent:qa:bug-123
+moltbot acp --session agent:main:main
+moltbot acp --session agent:design:main
+moltbot acp --session agent:qa:bug-123
 ```
 
 Each ACP session maps to a single Gateway session key. One agent can have many
@@ -90,9 +90,9 @@ Add a custom ACP agent in `~/.config/zed/settings.json` (or use Zed’s Settings
 ```json
 {
   "agent_servers": {
-    "Pigbot ACP": {
+    "Moltbot ACP": {
       "type": "custom",
-      "command": "pigbot",
+      "command": "moltbot",
       "args": ["acp"],
       "env": {}
     }
@@ -105,9 +105,9 @@ To target a specific Gateway or agent:
 ```json
 {
   "agent_servers": {
-    "Pigbot ACP": {
+    "Moltbot ACP": {
       "type": "custom",
-      "command": "pigbot",
+      "command": "moltbot",
       "args": [
         "acp",
         "--url", "wss://gateway-host:18789",
@@ -120,7 +120,7 @@ To target a specific Gateway or agent:
 }
 ```
 
-In Zed, open the Agent panel and select “Pigbot ACP” to start a thread.
+In Zed, open the Agent panel and select “Moltbot ACP” to start a thread.
 
 ## Session mapping
 
@@ -160,7 +160,7 @@ Learn more about session keys at [/concepts/session](/concepts/session).
 ### `acp client` options
 
 - `--cwd <dir>`: working directory for the ACP session.
-- `--server <command>`: ACP server command (default: `pigbot`).
+- `--server <command>`: ACP server command (default: `moltbot`).
 - `--server-args <args...>`: extra arguments passed to the ACP server.
 - `--server-verbose`: enable verbose logging on the ACP server.
 - `--verbose, -v`: verbose client logging.

package/docs/cli/agent.md

@@ -1,10 +1,10 @@
 ---
-summary: "CLI reference for `pigbot agent` (send one agent turn via the Gateway)"
+summary: "CLI reference for `moltbot agent` (send one agent turn via the Gateway)"
 read_when:
   - You want to run one agent turn from scripts (optionally deliver reply)
 ---
 
-# `pigbot agent`
+# `moltbot agent`
 
 Run an agent turn via the Gateway (use `--local` for embedded).
 Use `--agent <id>` to target a configured agent directly.
@@ -15,8 +15,8 @@ Related:
 ## Examples
 
 ```bash
-pigbot agent --to +15555550123 --message "status update" --deliver
-pigbot agent --agent ops --message "Summarize logs"
-pigbot agent --session-id 1234 --message "Summarize inbox" --thinking medium
-pigbot agent --agent ops --message "Generate report" --deliver --reply-channel slack --reply-to "#reports"
+moltbot agent --to +15555550123 --message "status update" --deliver
+moltbot agent --agent ops --message "Summarize logs"
+moltbot agent --session-id 1234 --message "Summarize inbox" --thinking medium
+moltbot agent --agent ops --message "Generate report" --deliver --reply-channel slack --reply-to "#reports"
 ```

package/docs/cli/agents.md

@@ -1,10 +1,10 @@
 ---
-summary: "CLI reference for `pigbot agents` (list/add/delete/set identity)"
+summary: "CLI reference for `moltbot agents` (list/add/delete/set identity)"
 read_when:
   - You want multiple isolated agents (workspaces + routing + auth)
 ---
 
-# `pigbot agents`
+# `moltbot agents`
 
 Manage isolated agents (workspaces + auth + routing).
 
@@ -15,11 +15,11 @@ Related:
 ## Examples
 
 ```bash
-pigbot agents list
-pigbot agents add work --workspace ~/clawd-work
-pigbot agents set-identity --workspace ~/clawd --from-identity
-pigbot agents set-identity --agent main --avatar avatars/clawd.png
-pigbot agents delete work
+moltbot agents list
+moltbot agents add work --workspace ~/clawd-work
+moltbot agents set-identity --workspace ~/clawd --from-identity
+moltbot agents set-identity --agent main --avatar avatars/clawd.png
+moltbot agents delete work
 ```
 
 ## Identity files
@@ -41,13 +41,13 @@ Avatar paths resolve relative to the workspace root.
 Load from `IDENTITY.md`:
 
 ```bash
-pigbot agents set-identity --workspace ~/clawd --from-identity
+moltbot agents set-identity --workspace ~/clawd --from-identity
 ```
 
 Override fields explicitly:
 
 ```bash
-pigbot agents set-identity --agent main --name "Clawd" --emoji "🦞" --avatar avatars/clawd.png
+moltbot agents set-identity --agent main --name "Clawd" --emoji "🦞" --avatar avatars/clawd.png
 ```
 
 Config sample:

package/docs/cli/approvals.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `pigbot approvals` (exec approvals for gateway or node hosts)"
+summary: "CLI reference for `moltbot approvals` (exec approvals for gateway or node hosts)"
 read_when:
   - You want to edit exec approvals from the CLI
   - You need to manage allowlists on gateway or node hosts
 ---
 
-# `pigbot approvals`
+# `moltbot approvals`
 
 Manage exec approvals for the **local host**, **gateway host**, or a **node host**.
 By default, commands target the local approvals file on disk. Use `--gateway` to target the gateway, or `--node` to target a specific node.
@@ -17,32 +17,32 @@ Related:
 ## Common commands
 
 ```bash
-pigbot approvals get
-pigbot approvals get --node <id|name|ip>
-pigbot approvals get --gateway
+moltbot approvals get
+moltbot approvals get --node <id|name|ip>
+moltbot approvals get --gateway
 ```
 
 ## Replace approvals from a file
 
 ```bash
-pigbot approvals set --file ./exec-approvals.json
-pigbot approvals set --node <id|name|ip> --file ./exec-approvals.json
-pigbot approvals set --gateway --file ./exec-approvals.json
+moltbot approvals set --file ./exec-approvals.json
+moltbot approvals set --node <id|name|ip> --file ./exec-approvals.json
+moltbot approvals set --gateway --file ./exec-approvals.json
 ```
 
 ## Allowlist helpers
 
 ```bash
-pigbot approvals allowlist add "~/Projects/**/bin/rg"
-pigbot approvals allowlist add --agent main --node <id|name|ip> "/usr/bin/uptime"
-pigbot approvals allowlist add --agent "*" "/usr/bin/uname"
+moltbot approvals allowlist add "~/Projects/**/bin/rg"
+moltbot approvals allowlist add --agent main --node <id|name|ip> "/usr/bin/uptime"
+moltbot approvals allowlist add --agent "*" "/usr/bin/uname"
 
-pigbot approvals allowlist remove "~/Projects/**/bin/rg"
+moltbot approvals allowlist remove "~/Projects/**/bin/rg"
 ```
 
 ## Notes
 
-- `--node` uses the same resolver as `pigbot nodes` (id, name, ip, or id prefix).
+- `--node` uses the same resolver as `moltbot nodes` (id, name, ip, or id prefix).
 - `--agent` defaults to `"*"`, which applies to all agents.
 - The node host must advertise `system.execApprovals.get/set` (macOS app or headless node host).
-- Approvals files are stored per host at `~/.pigbot/exec-approvals.json`.
+- Approvals files are stored per host at `~/.clawdbot/exec-approvals.json`.

package/docs/cli/browser.md

@@ -1,14 +1,14 @@
 ---
-summary: "CLI reference for `pigbot browser` (profiles, tabs, actions, extension relay, remote serve)"
+summary: "CLI reference for `moltbot browser` (profiles, tabs, actions, extension relay)"
 read_when:
-  - You use `pigbot browser` and want examples for common tasks
-  - You want to control a remote browser via `browser.controlUrl`
+  - You use `moltbot browser` and want examples for common tasks
+  - You want to control a browser running on another machine via a node host
   - You want to use the Chrome extension relay (attach/detach via toolbar button)
 ---
 
-# `pigbot browser`
+# `moltbot browser`
 
-Manage Pigbot’s browser control server and run browser actions (tabs, snapshots, screenshots, navigation, clicks, typing).
+Manage Moltbot’s browser control server and run browser actions (tabs, snapshots, screenshots, navigation, clicks, typing).
 
 Related:
 - Browser tool + API: [Browser tool](/tools/browser)
@@ -16,44 +16,46 @@ Related:
 
 ## Common flags
 
-- `--url <controlUrl>`: override `browser.controlUrl` for this command invocation.
-- `--browser-profile <name>`: choose a browser profile (default comes from config).
+- `--url <gatewayWsUrl>`: Gateway WebSocket URL (defaults to config).
+- `--token <token>`: Gateway token (if required).
+- `--timeout <ms>`: request timeout (ms).
+- `--browser-profile <name>`: choose a browser profile (default from config).
 - `--json`: machine-readable output (where supported).
 
 ## Quick start (local)
 
 ```bash
-pigbot browser --browser-profile chrome tabs
-pigbot browser --browser-profile clawd start
-pigbot browser --browser-profile clawd open https://example.com
-pigbot browser --browser-profile clawd snapshot
+moltbot browser --browser-profile chrome tabs
+moltbot browser --browser-profile clawd start
+moltbot browser --browser-profile clawd open https://example.com
+moltbot browser --browser-profile clawd snapshot
 ```
 
 ## Profiles
 
 Profiles are named browser routing configs. In practice:
-- `clawd`: launches/attaches to a dedicated Pigbot-managed Chrome instance (isolated user data dir).
+- `clawd`: launches/attaches to a dedicated Moltbot-managed Chrome instance (isolated user data dir).
 - `chrome`: controls your existing Chrome tab(s) via the Chrome extension relay.
 
 ```bash
-pigbot browser profiles
-pigbot browser create-profile --name work --color "#FF5A36"
-pigbot browser delete-profile --name work
+moltbot browser profiles
+moltbot browser create-profile --name work --color "#FF5A36"
+moltbot browser delete-profile --name work
 ```
 
 Use a specific profile:
 
 ```bash
-pigbot browser --browser-profile work tabs
+moltbot browser --browser-profile work tabs
 ```
 
 ## Tabs
 
 ```bash
-pigbot browser tabs
-pigbot browser open https://docs.clawd.bot
-pigbot browser focus <targetId>
-pigbot browser close <targetId>
+moltbot browser tabs
+moltbot browser open https://docs.molt.bot
+moltbot browser focus <targetId>
+moltbot browser close <targetId>
 ```
 
 ## Snapshot / screenshot / actions
@@ -61,21 +63,21 @@ pigbot browser close <targetId>
 Snapshot:
 
 ```bash
-pigbot browser snapshot
+moltbot browser snapshot
 ```
 
 Screenshot:
 
 ```bash
-pigbot browser screenshot
+moltbot browser screenshot
 ```
 
 Navigate/click/type (ref-based UI automation):
 
 ```bash
-pigbot browser navigate https://example.com
-pigbot browser click <ref>
-pigbot browser type <ref> "hello"
+moltbot browser navigate https://example.com
+moltbot browser click <ref>
+moltbot browser type <ref> "hello"
 ```
 
 ## Chrome extension relay (attach via toolbar button)
@@ -85,22 +87,18 @@ This mode lets the agent control an existing Chrome tab that you attach manually
 Install the unpacked extension to a stable path:
 
 ```bash
-pigbot browser extension install
-pigbot browser extension path
+moltbot browser extension install
+moltbot browser extension path
 ```
 
 Then Chrome → `chrome://extensions` → enable “Developer mode” → “Load unpacked” → select the printed folder.
 
 Full guide: [Chrome extension](/tools/chrome-extension)
 
-## Remote browser control (`pigbot browser serve`)
+## Remote browser control (node host proxy)
 
-If the Gateway runs on a different machine than the browser, run a standalone browser control server on the machine that runs Chrome:
+If the Gateway runs on a different machine than the browser, run a **node host** on the machine that has Chrome/Brave/Edge/Chromium. The Gateway will proxy browser actions to that node (no separate browser control server required).
 
-```bash
-pigbot browser serve --bind 127.0.0.1 --port 18791 --token <token>
-```
-
-Then point the Gateway at it using `browser.controlUrl` + `browser.controlToken` (or `PIGBOT_BROWSER_CONTROL_TOKEN`).
+Use `gateway.nodes.browser.mode` to control auto-routing and `gateway.nodes.browser.node` to pin a specific node if multiple are connected.
 
-Security + TLS best-practices: [Browser tool](/tools/browser), [Tailscale](/gateway/tailscale), [Security](/gateway/security)
+Security + remote setup: [Browser tool](/tools/browser), [Remote access](/gateway/remote), [Tailscale](/gateway/tailscale), [Security](/gateway/security)

package/docs/cli/channels.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `pigbot channels` (accounts, status, login/logout, logs)"
+summary: "CLI reference for `moltbot channels` (accounts, status, login/logout, logs)"
 read_when:
   - You want to add/remove channel accounts (WhatsApp/Telegram/Discord/Google Chat/Slack/Mattermost (plugin)/Signal/iMessage)
   - You want to check channel status or tail channel logs
 ---
 
-# `pigbot channels`
+# `moltbot channels`
 
 Manage chat channel accounts and their runtime status on the Gateway.
 
@@ -16,43 +16,43 @@ Related docs:
 ## Common commands
 
 ```bash
-pigbot channels list
-pigbot channels status
-pigbot channels capabilities
-pigbot channels capabilities --channel discord --target channel:123
-pigbot channels resolve --channel slack "#general" "@jane"
-pigbot channels logs --channel all
+moltbot channels list
+moltbot channels status
+moltbot channels capabilities
+moltbot channels capabilities --channel discord --target channel:123
+moltbot channels resolve --channel slack "#general" "@jane"
+moltbot channels logs --channel all
 ```
 
 ## Add / remove accounts
 
 ```bash
-pigbot channels add --channel telegram --token <bot-token>
-pigbot channels remove --channel telegram --delete
+moltbot channels add --channel telegram --token <bot-token>
+moltbot channels remove --channel telegram --delete
 ```
 
-Tip: `pigbot channels add --help` shows per-channel flags (token, app token, signal-cli paths, etc).
+Tip: `moltbot channels add --help` shows per-channel flags (token, app token, signal-cli paths, etc).
 
 ## Login / logout (interactive)
 
 ```bash
-pigbot channels login --channel whatsapp
-pigbot channels logout --channel whatsapp
+moltbot channels login --channel whatsapp
+moltbot channels logout --channel whatsapp
 ```
 
 ## Troubleshooting
 
-- Run `pigbot status --deep` for a broad probe.
-- Use `pigbot doctor` for guided fixes.
-- `pigbot channels list` prints `Claude: HTTP 403 ... user:profile` → usage snapshot needs the `user:profile` scope. Use `--no-usage`, or provide a claude.ai session key (`CLAUDE_WEB_SESSION_KEY` / `CLAUDE_WEB_COOKIE`), or re-auth via Claude Code CLI.
+- Run `moltbot status --deep` for a broad probe.
+- Use `moltbot doctor` for guided fixes.
+- `moltbot channels list` prints `Claude: HTTP 403 ... user:profile` → usage snapshot needs the `user:profile` scope. Use `--no-usage`, or provide a claude.ai session key (`CLAUDE_WEB_SESSION_KEY` / `CLAUDE_WEB_COOKIE`), or re-auth via Claude Code CLI.
 
 ## Capabilities probe
 
 Fetch provider capability hints (intents/scopes where available) plus static feature support:
 
 ```bash
-pigbot channels capabilities
-pigbot channels capabilities --channel discord --target channel:123
+moltbot channels capabilities
+moltbot channels capabilities --channel discord --target channel:123
 ```
 
 Notes:
@@ -65,9 +65,9 @@ Notes:
 Resolve channel/user names to IDs using the provider directory:
 
 ```bash
-pigbot channels resolve --channel slack "#general" "@jane"
-pigbot channels resolve --channel discord "My Server/#support" "@someone"
-pigbot channels resolve --channel matrix "Project Room"
+moltbot channels resolve --channel slack "#general" "@jane"
+moltbot channels resolve --channel discord "My Server/#support" "@someone"
+moltbot channels resolve --channel matrix "Project Room"
 ```
 
 Notes:

package/docs/cli/config.md

@@ -1,22 +1,22 @@
 ---
-summary: "CLI reference for `pigbot config` (get/set/unset config values)"
+summary: "CLI reference for `moltbot config` (get/set/unset config values)"
 read_when:
   - You want to read or edit config non-interactively
 ---
 
-# `pigbot config`
+# `moltbot config`
 
 Config helpers: get/set/unset values by path. Run without a subcommand to open
-the configure wizard (same as `pigbot configure`).
+the configure wizard (same as `moltbot configure`).
 
 ## Examples
 
 ```bash
-pigbot config get browser.executablePath
-pigbot config set browser.executablePath "/usr/bin/google-chrome"
-pigbot config set agents.defaults.heartbeat.every "2h"
-pigbot config set agents.list[0].tools.exec.node "node-id-or-name"
-pigbot config unset tools.web.search.apiKey
+moltbot config get browser.executablePath
+moltbot config set browser.executablePath "/usr/bin/google-chrome"
+moltbot config set agents.defaults.heartbeat.every "2h"
+moltbot config set agents.list[0].tools.exec.node "node-id-or-name"
+moltbot config unset tools.web.search.apiKey
 ```
 
 ## Paths
@@ -24,15 +24,15 @@ pigbot config unset tools.web.search.apiKey
 Paths use dot or bracket notation:
 
 ```bash
-pigbot config get agents.defaults.workspace
-pigbot config get agents.list[0].id
+moltbot config get agents.defaults.workspace
+moltbot config get agents.list[0].id
 ```
 
 Use the agent list index to target a specific agent:
 
 ```bash
-pigbot config get agents.list
-pigbot config set agents.list[1].tools.exec.node "node-id-or-name"
+moltbot config get agents.list
+moltbot config set agents.list[1].tools.exec.node "node-id-or-name"
 ```
 
 ## Values
@@ -41,9 +41,9 @@ Values are parsed as JSON5 when possible; otherwise they are treated as strings.
 Use `--json` to require JSON5 parsing.
 
 ```bash
-pigbot config set agents.defaults.heartbeat.every "0m"
-pigbot config set gateway.port 19001 --json
-pigbot config set channels.whatsapp.groups '["*"]' --json
+moltbot config set agents.defaults.heartbeat.every "0m"
+moltbot config set gateway.port 19001 --json
+moltbot config set channels.whatsapp.groups '["*"]' --json
 ```
 
 Restart the gateway after edits.

package/docs/cli/configure.md

@@ -1,18 +1,18 @@
 ---
-summary: "CLI reference for `pigbot configure` (interactive configuration prompts)"
+summary: "CLI reference for `moltbot configure` (interactive configuration prompts)"
 read_when:
   - You want to tweak credentials, devices, or agent defaults interactively
 ---
 
-# `pigbot configure`
+# `moltbot configure`
 
 Interactive prompt to set up credentials, devices, and agent defaults.
 
 Note: The **Model** section now includes a multi-select for the
 `agents.defaults.models` allowlist (what shows up in `/model` and the model picker).
 
-Tip: `pigbot config` without a subcommand opens the same wizard. Use
-`pigbot config get|set|unset` for non-interactive edits.
+Tip: `moltbot config` without a subcommand opens the same wizard. Use
+`moltbot config get|set|unset` for non-interactive edits.
 
 Related:
 - Gateway configuration reference: [Configuration](/gateway/configuration)
@@ -25,6 +25,6 @@ Notes:
 ## Examples
 
 ```bash
-pigbot configure
-pigbot configure --section models --section channels
+moltbot configure
+moltbot configure --section models --section channels
 ```

package/docs/cli/cron.md

@@ -1,29 +1,29 @@
 ---
-summary: "CLI reference for `pigbot cron` (schedule and run background jobs)"
+summary: "CLI reference for `moltbot cron` (schedule and run background jobs)"
 read_when:
   - You want scheduled jobs and wakeups
   - You’re debugging cron execution and logs
 ---
 
-# `pigbot cron`
+# `moltbot cron`
 
 Manage cron jobs for the Gateway scheduler.
 
 Related:
 - Cron jobs: [Cron jobs](/automation/cron-jobs)
 
-Tip: run `pigbot cron --help` for the full command surface.
+Tip: run `moltbot cron --help` for the full command surface.
 
 ## Common edits
 
 Update delivery settings without changing the message:
 
 ```bash
-pigbot cron edit <job-id> --deliver --channel telegram --to "123456789"
+moltbot cron edit <job-id> --deliver --channel telegram --to "123456789"
 ```
 
 Disable delivery for an isolated job:
 
 ```bash
-pigbot cron edit <job-id> --no-deliver
+moltbot cron edit <job-id> --no-deliver
 ```

package/docs/cli/dashboard.md

@@ -1,16 +1,16 @@
 ---
-summary: "CLI reference for `pigbot dashboard` (open the Control UI)"
+summary: "CLI reference for `moltbot dashboard` (open the Control UI)"
 read_when:
   - You want to open the Control UI with your current token
   - You want to print the URL without launching a browser
 ---
 
-# `pigbot dashboard`
+# `moltbot dashboard`
 
 Open the Control UI using your current auth.
 
 ```bash
-pigbot dashboard
-pigbot dashboard --no-open
+moltbot dashboard
+moltbot dashboard --no-open
 ```