Rename clawdbot to moltbot throughout codebase

Comprehensive rename from Clawdbot to Moltbot to align with the public rebrand.
The underlying CLI tool is still named 'clawdbot' so internal paths and CLI
commands remain unchanged.

File renames:
- start-clawdbot.sh -> start-moltbot.sh
- clawdbot.json.template -> moltbot.json.template

Code renames:
- ClawdbotEnv -> MoltbotEnv
- CLAWDBOT_PORT -> MOLTBOT_PORT
- CLAWDBOT_BUCKET -> MOLTBOT_BUCKET
- CLAWDBOT_GATEWAY_TOKEN -> MOLTBOT_GATEWAY_TOKEN (user-facing env var)
- findExistingClawdbotProcess -> findExistingMoltbotProcess
- ensureClawdbotGateway -> ensureMoltbotGateway
- R2 bucket: clawdbot-data -> moltbot-data
- R2 mount path: /data/clawdbot -> /data/moltbot
- Sandbox ID: 'clawdbot' -> 'moltbot'

UI updates:
- Admin page title: 'Clawdbot Admin' -> 'Moltbot Admin'
- index.html title updated

Documentation updates:
- README.md updated with new bucket name
- AGENTS.md fully updated with new naming
- .dev.vars.example updated

Unchanged (container still uses these internally):
- /root/.clawdbot (config directory)
- clawdbot.json (config file)
- clawdbot CLI commands (devices list, gateway, etc.)
- CLAWDBOT_GATEWAY_TOKEN, CLAWDBOT_DEV_MODE (container env vars mapped from user-facing names)

Author: brianbrunner

.dev.vars.example

@@ -10,7 +10,7 @@ DEV_MODE=true
 DEBUG_ROUTES=true
 
 # Optional - set a fixed token instead of auto-generated
-CLAWDBOT_GATEWAY_TOKEN=dev-token-change-in-prod
+MOLTBOT_GATEWAY_TOKEN=dev-token-change-in-prod
 
 # Cloudflare Access configuration for /_admin and /api routes
 # Required for admin UI and device pairing API in production

AGENTS.md

@@ -4,12 +4,14 @@ Guidelines for AI agents working on this codebase.
 
 ## Project Overview
 
-This is a Cloudflare Worker that runs [Clawdbot](https://clawd.bot/) in a Cloudflare Sandbox container. It provides:
-- Proxying to the Clawdbot gateway (web UI + WebSocket)
+This is a Cloudflare Worker that runs [Moltbot](https://molt.bot/) in a Cloudflare Sandbox container. It provides:
+- Proxying to the Moltbot gateway (web UI + WebSocket)
 - Admin UI at `/_admin/` for device management
 - API endpoints at `/api/*` for device pairing
 - Debug endpoints at `/debug/*` for troubleshooting
 
+**Note:** The CLI tool is still named `clawdbot` (upstream hasn't renamed yet), so CLI commands and internal config paths still use that name.
+
 ## Project Structure
 
 ```
@@ -21,7 +23,7 @@ src/
 │   ├── jwt.ts        # JWT verification
 │   ├── jwks.ts       # JWKS fetching and caching
 │   └── middleware.ts # Hono middleware for auth
-├── gateway/          # Clawdbot gateway management
+├── gateway/          # Moltbot gateway management
 │   ├── process.ts    # Process lifecycle (find, start)
 │   ├── env.ts        # Environment variable building
 │   ├── r2.ts         # R2 bucket mounting
@@ -43,11 +45,12 @@ src/
 
 - `DEV_MODE` - Skips CF Access auth AND bypasses device pairing (maps to `CLAWDBOT_DEV_MODE` for container)
 - `DEBUG_ROUTES` - Enables `/debug/*` routes (disabled by default)
-- See `src/types.ts` for full `ClawdbotEnv` interface
+- See `src/types.ts` for full `MoltbotEnv` interface
 
 ### CLI Commands
 
-When calling the clawdbot CLI from the worker, always include `--url ws://localhost:18789`:
+When calling the moltbot CLI from the worker, always include `--url ws://localhost:18789`.
+Note: The CLI is still named `clawdbot` until upstream renames it:
 ```typescript
 sandbox.startProcess('clawdbot devices list --json --url ws://localhost:18789')
 ```
@@ -111,7 +114,7 @@ Browser
    ▼
 ┌─────────────────────────────────────┐
 │     Cloudflare Worker (index.ts)    │
-│  - Starts Clawdbot in sandbox       │
+│  - Starts Moltbot in sandbox        │
 │  - Proxies HTTP/WebSocket requests  │
 │  - Passes secrets as env vars       │
 └──────────────┬──────────────────────┘
@@ -120,7 +123,7 @@ Browser
 ┌─────────────────────────────────────┐
 │     Cloudflare Sandbox Container    │
 │  ┌───────────────────────────────┐  │
-│  │     Clawdbot Gateway          │  │
+│  │     Moltbot Gateway           │  │
 │  │  - Control UI on port 18789   │  │
 │  │  - WebSocket RPC protocol     │  │
 │  │  - Agent runtime              │  │
@@ -133,9 +136,9 @@ Browser
 | File | Purpose |
 |------|---------|
 | `src/index.ts` | Worker that manages sandbox lifecycle and proxies requests |
-| `Dockerfile` | Container image based on `cloudflare/sandbox` with Node 22 + Clawdbot |
-| `start-clawdbot.sh` | Startup script that configures clawdbot from env vars and launches gateway |
-| `clawdbot.json.template` | Default Clawdbot configuration template |
+| `Dockerfile` | Container image based on `cloudflare/sandbox` with Node 22 + Moltbot |
+| `start-moltbot.sh` | Startup script that configures moltbot from env vars and launches gateway |
+| `moltbot.json.template` | Default Moltbot configuration template |
 | `wrangler.jsonc` | Cloudflare Worker + Container configuration |
 
 ## Local Development
@@ -163,42 +166,44 @@ Local development with `wrangler dev` has issues proxying WebSocket connections
 
 ## Docker Image Caching
 
-The Dockerfile includes a cache bust comment. When changing `clawdbot.json.template` or `start-clawdbot.sh`, bump the version:
+The Dockerfile includes a cache bust comment. When changing `moltbot.json.template` or `start-moltbot.sh`, bump the version:
 
 ```dockerfile
 # Build cache bust: 2026-01-26-v10
 ```
 
 ## Gateway Configuration
 
-Clawdbot configuration is built at container startup:
+Moltbot configuration is built at container startup:
 
-1. `clawdbot.json.template` is copied to `~/.clawdbot/clawdbot.json`
-2. `start-clawdbot.sh` updates the config with values from environment variables
+1. `moltbot.json.template` is copied to `~/.clawdbot/clawdbot.json` (internal path unchanged)
+2. `start-moltbot.sh` updates the config with values from environment variables
 3. Gateway starts with `--allow-unconfigured` flag (skips onboarding wizard)
 
 ### Container Environment Variables
 
+These are the env vars passed TO the container (internal names):
+
 | Variable | Config Path | Notes |
 |----------|-------------|-------|
-| `ANTHROPIC_API_KEY` | (env var) | Clawdbot reads directly from env |
-| `CLAWDBOT_GATEWAY_TOKEN` | `--token` flag | If not set, random token is generated |
-| `CLAWDBOT_DEV_MODE` | `controlUi.allowInsecureAuth` | Set to `true` for local dev (allows HTTP auth) |
+| `ANTHROPIC_API_KEY` | (env var) | Moltbot reads directly from env |
+| `CLAWDBOT_GATEWAY_TOKEN` | `--token` flag | Mapped from `MOLTBOT_GATEWAY_TOKEN` |
+| `CLAWDBOT_DEV_MODE` | `controlUi.allowInsecureAuth` | Mapped from `DEV_MODE` |
 | `TELEGRAM_BOT_TOKEN` | `channels.telegram.botToken` | |
 | `DISCORD_BOT_TOKEN` | `channels.discord.token` | |
 | `SLACK_BOT_TOKEN` | `channels.slack.botToken` | |
 | `SLACK_APP_TOKEN` | `channels.slack.appToken` | |
 
-## Clawdbot Config Schema
+## Moltbot Config Schema
 
-Clawdbot has strict config validation. Common gotchas:
+Moltbot has strict config validation. Common gotchas:
 
 - `agents.defaults.model` must be `{ "primary": "model/name" }` not a string
 - `gateway.mode` must be `"local"` for headless operation
 - No `webchat` channel - the Control UI is served automatically
 - `gateway.bind` is not a config option - use `--bind` CLI flag
 
-See [Clawdbot docs](https://docs.clawd.bot/gateway/configuration) for full schema.
+See [Moltbot docs](https://docs.molt.bot/gateway/configuration) for full schema.
 
 ## Common Tasks
 
@@ -211,7 +216,7 @@ See [Clawdbot docs](https://docs.clawd.bot/gateway/configuration) for full schem
 
 ### Adding a New Environment Variable
 
-1. Add to `ClawdbotEnv` interface in `src/types.ts`
+1. Add to `MoltbotEnv` interface in `src/types.ts`
 2. If passed to container, add to `buildEnvVars()` in `src/gateway/env.ts`
 3. Update `.dev.vars.example`
 4. Document in README.md secrets table
@@ -230,12 +235,12 @@ Enable debug routes with `DEBUG_ROUTES=true` and check `/debug/processes`.
 
 ## R2 Storage Notes
 
-R2 is mounted via s3fs at `/data/clawdbot`. Important gotchas:
+R2 is mounted via s3fs at `/data/moltbot`. Important gotchas:
 
 - **rsync compatibility**: Use `rsync -r --no-times` instead of `rsync -a`. s3fs doesn't support setting timestamps, which causes rsync to fail with "Input/output error".
 
 - **Mount checking**: Don't rely on `sandbox.mountBucket()` error messages to detect "already mounted" state. Instead, check `mount | grep s3fs` to verify the mount status.
 
-- **Never delete R2 data**: The mount directory `/data/clawdbot` IS the R2 bucket. Running `rm -rf /data/clawdbot/*` will DELETE your backup data. Always check mount status before any destructive operations.
+- **Never delete R2 data**: The mount directory `/data/moltbot` IS the R2 bucket. Running `rm -rf /data/moltbot/*` will DELETE your backup data. Always check mount status before any destructive operations.
 
 - **Process status**: The sandbox API's `proc.status` may not update immediately after a process completes. Instead of checking `proc.status === 'completed'`, verify success by checking for expected output (e.g., timestamp file exists after sync).

Dockerfile

@@ -14,25 +14,25 @@ RUN apt-get update && apt-get install -y xz-utils ca-certificates rsync \
 # Install pnpm globally
 RUN npm install -g pnpm
 
-# Install clawdbot globally
-RUN npm install -g clawdbot@latest \
+# Install moltbot (CLI is still named clawdbot until upstream renames)
+# Pin to specific version for reproducible builds
+RUN npm install -g clawdbot@2026.1.24-3 \
     && clawdbot --version
 
-# Create clawdbot directories
-# Note: When R2 is mounted, CLAWDBOT_STATE_DIR env var points to the mount path
+# Create moltbot directories (paths still use clawdbot until upstream renames)
 # Templates are stored in /root/.clawdbot-templates for initialization
 RUN mkdir -p /root/.clawdbot \
     && mkdir -p /root/.clawdbot-templates \
     && mkdir -p /root/clawd \
     && mkdir -p /root/clawd/skills
 
 # Copy startup script
-# Build cache bust: 2026-01-28-v22-force-rebuild
-COPY start-clawdbot.sh /usr/local/bin/start-clawdbot.sh
-RUN chmod +x /usr/local/bin/start-clawdbot.sh
+# Build cache bust: 2026-01-28-v23-moltbot-rename
+COPY start-moltbot.sh /usr/local/bin/start-moltbot.sh
+RUN chmod +x /usr/local/bin/start-moltbot.sh
 
 # Copy default configuration template
-COPY clawdbot.json.template /root/.clawdbot-templates/clawdbot.json.template
+COPY moltbot.json.template /root/.clawdbot-templates/moltbot.json.template
 
 # Set working directory
 WORKDIR /root/clawd

README.md

@@ -61,9 +61,9 @@ npx wrangler secret put ANTHROPIC_API_KEY
 
 # Generate and set a gateway token (required for remote access)
 # Save this token - you'll need it to access the Control UI
-export CLAWDBOT_GATEWAY_TOKEN=$(openssl rand -base64 32 | tr -d '=+/' | head -c 32)
-echo "Your gateway token: $CLAWDBOT_GATEWAY_TOKEN"
-echo "$CLAWDBOT_GATEWAY_TOKEN" | npx wrangler secret put CLAWDBOT_GATEWAY_TOKEN
+export MOLTBOT_GATEWAY_TOKEN=$(openssl rand -base64 32 | tr -d '=+/' | head -c 32)
+echo "Your gateway token: $MOLTBOT_GATEWAY_TOKEN"
+echo "$MOLTBOT_GATEWAY_TOKEN" | npx wrangler secret put MOLTBOT_GATEWAY_TOKEN
 
 # Deploy
 npm run deploy
@@ -182,7 +182,7 @@ By default, moltbot data (configs, paired devices, conversation history) is lost
 1. Go to **R2** > **Overview** in the [Cloudflare Dashboard](https://dash.cloudflare.com/)
 2. Click **Manage R2 API Tokens**
 3. Create a new token with **Object Read & Write** permissions
-4. Select the `clawdbot-data` bucket (created automatically on first deploy)
+4. Select the `moltbot-data` bucket (created automatically on first deploy)
 5. Copy the **Access Key ID** and **Secret Access Key**
 
 ### 2. Set Secrets
@@ -205,11 +205,11 @@ To find your Account ID: Go to the [Cloudflare Dashboard](https://dash.cloudflar
 R2 storage uses a backup/restore approach for simplicity:
 
 **On container startup:**
-- If R2 is mounted and contains backup data, it's restored to `/root/.clawdbot`
+- If R2 is mounted and contains backup data, it's restored to the moltbot config directory
 - Moltbot uses its default paths (no special configuration needed)
 
 **During operation:**
-- A cron job runs every 5 minutes to sync `/root/.clawdbot` → R2
+- A cron job runs every 5 minutes to sync the moltbot config to R2
 - You can also trigger a manual backup from the admin UI at `/_admin/`
 
 **In the admin UI:**
@@ -338,7 +338,7 @@ npm run deploy
 | `OPENAI_API_KEY` | No | OpenAI API key (alternative to Anthropic) |
 | `CF_ACCESS_TEAM_DOMAIN` | Yes* | Cloudflare Access team domain (required for admin UI) |
 | `CF_ACCESS_AUD` | Yes* | Cloudflare Access application audience (required for admin UI) |
-| `CLAWDBOT_GATEWAY_TOKEN` | Yes | Gateway token for authentication (pass via `?token=` query param) |
+| `MOLTBOT_GATEWAY_TOKEN` | Yes | Gateway token for authentication (pass via `?token=` query param) |
 | `DEV_MODE` | No | Set to `true` to skip CF Access auth + device pairing (local dev only) |
 | `DEBUG_ROUTES` | No | Set to `true` to enable `/debug/*` routes |
 | `SANDBOX_SLEEP_AFTER` | No | Container sleep timeout: `never` (default) or duration like `10m`, `1h` |

index.html

@@ -3,7 +3,7 @@
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Clawdbot Admin</title>
+    <title>Moltbot Admin</title>
   </head>
   <body>
     <div id="root"></div>

clawdbot.json.template moltbot.json.templateclawdbot.json.template renamed to moltbot.json.template

@@ -17,6 +17,7 @@
   },
   "dependencies": {
     "@cloudflare/puppeteer": "^1.0.5",
+    "@cloudflare/townlake-trino-client": "^0.2.0",
     "hono": "^4.11.6",
     "react": "^19.0.0",
     "react-dom": "^19.0.0"

package-lock.json

@@ -121,14 +121,23 @@
       margin-top: 8px;
     }
 
+    .instructions a {
+      color: rgb(244, 129, 32);
+      text-decoration: none;
+    }
+    
+    .instructions a:hover {
+      text-decoration: underline;
+    }
+    
     .info {
       font-size: 0.8rem;
       color: #707070;
       margin-top: 30px;
     }
 
     .info a {
-      color: #60a5fa;
+      color: rgb(244, 129, 32);
       text-decoration: none;
     }
 
@@ -156,15 +165,14 @@ <h2>Missing Variables</h2>
       <h2>How to Fix</h2>
       <p>Set the missing secrets using the Wrangler CLI:</p>
       <pre>wrangler secret put &lt;VARIABLE_NAME&gt;</pre>
-      <p style="margin-top: 16px; margin-bottom: 0;">
+      <p style="margin-top: 16px;">
         For example: <code>wrangler secret put ANTHROPIC_API_KEY</code>
       </p>
+      <p style="margin-bottom: 0;">
+        After setting the secrets, refresh this page to continue.
+        See the <a href="https://github.com/cloudflare/moltworker" target="_blank">README</a> for full setup instructions.
+      </p>
     </div>
-    
-    <p class="info">
-      After setting the secrets, refresh this page to continue.<br>
-      See the <a href="https://github.com/cloudflare/moltworker" target="_blank">README</a> for full setup instructions.
-    </p>
   </div>
 </body>
 </html>

package.json

@@ -37,7 +37,7 @@
 
     @keyframes pulse {
       0%, 100% { opacity: 1; transform: scale(1); }
-      50% { opacity: 0.95; transform: scale(0.98); }
+      50% { opacity: 0.9; transform: scale(0.95); }
     }
 
     h1 {