refactor: rename clawdbot to moltbot with legacy compat

This commit is contained in:
Peter Steinberger
2026-01-27 12:19:58 +00:00
parent 83460df96f
commit 6d16a658e5
1839 changed files with 11250 additions and 11199 deletions

View File

@@ -1,12 +1,12 @@
---
summary: "End-to-end guide for running Clawdbot as a personal assistant with safety cautions"
summary: "End-to-end guide for running Moltbot as a personal assistant with safety cautions"
read_when:
- Onboarding a new assistant instance
- Reviewing safety/permission implications
---
# Building a personal assistant with Clawdbot (Clawd-style)
# Building a personal assistant with Moltbot (Clawd-style)
Clawdbot is a WhatsApp + Telegram + Discord + iMessage gateway for **Pi** agents. Plugins add Mattermost. This guide is the "personal assistant" setup: one dedicated WhatsApp number that behaves like your always-on agent.
Moltbot is a WhatsApp + Telegram + Discord + iMessage gateway for **Pi** agents. Plugins add Mattermost. This guide is the "personal assistant" setup: one dedicated WhatsApp number that behaves like your always-on agent.
## ⚠️ Safety first
@@ -23,19 +23,19 @@ Start conservative:
## Prerequisites
- Node **22+**
- Clawdbot available on PATH (recommended: global install)
- Moltbot available on PATH (recommended: global install)
- A second phone number (SIM/eSIM/prepaid) for the assistant
```bash
npm install -g clawdbot@latest
# or: pnpm add -g clawdbot@latest
npm install -g moltbot@latest
# or: pnpm add -g moltbot@latest
```
From source (development):
```bash
git clone https://github.com/clawdbot/clawdbot.git
cd clawdbot
git clone https://github.com/moltbot/moltbot.git
cd moltbot
pnpm install
pnpm ui:build # auto-installs UI deps on first run
pnpm build
@@ -56,28 +56,28 @@ Your Phone (personal) Second Phone (assistant)
┌─────────────────┐
│ Your Mac │
│ (clawdbot) │
│ (moltbot) │
│ Pi agent │
└─────────────────┘
```
If you link your personal WhatsApp to Clawdbot, every message to you becomes “agent input”. Thats rarely what you want.
If you link your personal WhatsApp to Moltbot, every message to you becomes “agent input”. Thats rarely what you want.
## 5-minute quick start
1) Pair WhatsApp Web (shows QR; scan with the assistant phone):
```bash
clawdbot channels login
moltbot channels login
```
2) Start the Gateway (leave it running):
```bash
clawdbot gateway --port 18789
moltbot gateway --port 18789
```
3) Put a minimal config in `~/.clawdbot/clawdbot.json`:
3) Put a minimal config in `~/.clawdbot/moltbot.json`:
```json5
{
@@ -87,18 +87,18 @@ clawdbot gateway --port 18789
Now message the assistant number from your allowlisted phone.
When onboarding finishes, we auto-open the dashboard with your gateway token and print the tokenized link. To reopen later: `clawdbot dashboard`.
When onboarding finishes, we auto-open the dashboard with your gateway token and print the tokenized link. To reopen later: `moltbot dashboard`.
## Give the agent a workspace (AGENTS)
Clawd reads operating instructions and “memory” from its workspace directory.
By default, Clawdbot uses `~/clawd` as the agent workspace, and will create it (plus starter `AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`) automatically on setup/first agent run. `BOOTSTRAP.md` is only created when the workspace is brand new (it should not come back after you delete it).
By default, Moltbot uses `~/clawd` as the agent workspace, and will create it (plus starter `AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`) automatically on setup/first agent run. `BOOTSTRAP.md` is only created when the workspace is brand new (it should not come back after you delete it).
Tip: treat this folder like Clawds “memory” and make it a git repo (ideally private) so your `AGENTS.md` + memory files are backed up. If git is installed, brand-new workspaces are auto-initialized.
```bash
clawdbot setup
moltbot setup
```
Full workspace layout + backup guide: [Agent workspace](/concepts/agent-workspace)
@@ -126,7 +126,7 @@ If you already ship your own workspace files from a repo, you can disable bootst
## The config that turns it into “an assistant”
Clawdbot defaults to a good assistant setup, but youll usually want to tune:
Moltbot defaults to a good assistant setup, but youll usually want to tune:
- persona/instructions in `SOUL.md`
- thinking defaults (if desired)
- heartbeats (once you trust it)
@@ -178,13 +178,13 @@ Example:
## Heartbeats (proactive mode)
By default, Clawdbot runs a heartbeat every 30 minutes with the prompt:
By default, Moltbot runs a heartbeat every 30 minutes with the prompt:
`Read HEARTBEAT.md if it exists (workspace context). Follow it strictly. Do not infer or repeat old tasks from prior chats. If nothing needs attention, reply HEARTBEAT_OK.`
Set `agents.defaults.heartbeat.every: "0m"` to disable.
- If `HEARTBEAT.md` exists but is effectively empty (only blank lines and markdown headers like `# Heading`), Clawdbot skips the heartbeat run to save API calls.
- If `HEARTBEAT.md` exists but is effectively empty (only blank lines and markdown headers like `# Heading`), Moltbot skips the heartbeat run to save API calls.
- If the file is missing, the heartbeat still runs and the model decides what to do.
- If the agent replies with `HEARTBEAT_OK` (optionally with short padding; see `agents.defaults.heartbeat.ackMaxChars`), Clawdbot suppresses outbound delivery for that heartbeat.
- If the agent replies with `HEARTBEAT_OK` (optionally with short padding; see `agents.defaults.heartbeat.ackMaxChars`), Moltbot suppresses outbound delivery for that heartbeat.
- Heartbeats run full agent turns — shorter intervals burn more tokens.
```json5
@@ -209,25 +209,25 @@ Heres the screenshot.
MEDIA:/tmp/screenshot.png
```
Clawdbot extracts these and sends them as media alongside the text.
Moltbot extracts these and sends them as media alongside the text.
## Operations checklist
```bash
clawdbot status # local status (creds, sessions, queued events)
clawdbot status --all # full diagnosis (read-only, pasteable)
clawdbot status --deep # adds gateway health probes (Telegram + Discord)
clawdbot health --json # gateway health snapshot (WS)
moltbot status # local status (creds, sessions, queued events)
moltbot status --all # full diagnosis (read-only, pasteable)
moltbot status --deep # adds gateway health probes (Telegram + Discord)
moltbot health --json # gateway health snapshot (WS)
```
Logs live under `/tmp/clawdbot/` (default: `clawdbot-YYYY-MM-DD.log`).
Logs live under `/tmp/moltbot/` (default: `moltbot-YYYY-MM-DD.log`).
## Next steps
- WebChat: [WebChat](/web/webchat)
- Gateway ops: [Gateway runbook](/gateway)
- Cron + wakeups: [Cron jobs](/automation/cron-jobs)
- macOS menu bar companion: [Clawdbot macOS app](/platforms/macos)
- macOS menu bar companion: [Moltbot macOS app](/platforms/macos)
- iOS node app: [iOS app](/platforms/ios)
- Android node app: [Android app](/platforms/android)
- Windows status: [Windows (WSL2)](/platforms/windows)

View File

@@ -9,11 +9,11 @@ read_when:
Goal: go from **zero****first working chat** (with sane defaults) as quickly as possible.
Fastest chat: open the Control UI (no channel setup needed). Run `clawdbot dashboard`
Fastest chat: open the Control UI (no channel setup needed). Run `moltbot dashboard`
and chat in the browser, or open `http://127.0.0.1:18789/` on the gateway host.
Docs: [Dashboard](/web/dashboard) and [Control UI](/web/control-ui).
Recommended path: use the **CLI onboarding wizard** (`clawdbot onboard`). It sets up:
Recommended path: use the **CLI onboarding wizard** (`moltbot onboard`). It sets up:
- model/auth (OAuth recommended)
- gateway settings
- channels (WhatsApp/Telegram/Discord/Mattermost (plugin)/...)
@@ -45,7 +45,7 @@ run on host, set an explicit per-agent override:
- Node `>=22`
- `pnpm` (optional; recommended if you build from source)
- **Recommended:** Brave Search API key for web search. Easiest path:
`clawdbot configure --section web` (stores `tools.web.search.apiKey`).
`moltbot configure --section web` (stores `tools.web.search.apiKey`).
See [Web tools](/tools/web).
macOS: if you plan to build the apps, install Xcode / CLT. For the CLI + gateway only, Node is enough.
@@ -68,17 +68,17 @@ iwr -useb https://molt.bot/install.ps1 | iex
Alternative (global install):
```bash
npm install -g clawdbot@latest
npm install -g moltbot@latest
```
```bash
pnpm add -g clawdbot@latest
pnpm add -g moltbot@latest
```
## 2) Run the onboarding wizard (and install the service)
```bash
clawdbot onboard --install-daemon
moltbot onboard --install-daemon
```
What youll choose:
@@ -105,13 +105,13 @@ Headless/server tip: do OAuth on a normal machine first, then copy `oauth.json`
If you installed the service during onboarding, the Gateway should already be running:
```bash
clawdbot gateway status
moltbot gateway status
```
Manual run (foreground):
```bash
clawdbot gateway --port 18789 --verbose
moltbot gateway --port 18789 --verbose
```
Dashboard (local loopback): `http://127.0.0.1:18789/`
@@ -123,9 +123,9 @@ channels. If you use WhatsApp or Telegram, run the Gateway with **Node**.
## 3.5) Quick verify (2 min)
```bash
clawdbot status
clawdbot health
clawdbot security audit --deep
moltbot status
moltbot health
moltbot security audit --deep
```
## 4) Pair + connect your first chat surface
@@ -133,7 +133,7 @@ clawdbot security audit --deep
### WhatsApp (QR login)
```bash
clawdbot channels login
moltbot channels login
```
Scan via WhatsApp → Settings → Linked Devices.
@@ -155,26 +155,26 @@ Default posture: unknown DMs get a short code and messages are not processed unt
If your first DM gets no reply, approve the pairing:
```bash
clawdbot pairing list whatsapp
clawdbot pairing approve whatsapp <code>
moltbot pairing list whatsapp
moltbot pairing approve whatsapp <code>
```
Pairing doc: [Pairing](/start/pairing)
## From source (development)
If youre hacking on Clawdbot itself, run from source:
If youre hacking on Moltbot itself, run from source:
```bash
git clone https://github.com/clawdbot/clawdbot.git
cd clawdbot
git clone https://github.com/moltbot/moltbot.git
cd moltbot
pnpm install
pnpm ui:build # auto-installs UI deps on first run
pnpm build
clawdbot onboard --install-daemon
moltbot onboard --install-daemon
```
If you dont have a global install yet, run the onboarding step via `pnpm clawdbot ...` from the repo.
If you dont have a global install yet, run the onboarding step via `pnpm moltbot ...` from the repo.
`pnpm build` also bundles A2UI assets; if you need to run just that step, use `pnpm canvas:a2ui:bundle`.
Gateway (from this repo):
@@ -188,13 +188,13 @@ node dist/entry.js gateway --port 18789 --verbose
In a new terminal, send a test message:
```bash
clawdbot message send --target +15555550123 --message "Hello from Clawdbot"
moltbot message send --target +15555550123 --message "Hello from Moltbot"
```
If `clawdbot health` shows “no auth configured”, go back to the wizard and set OAuth/key auth — the agent wont be able to respond without it.
If `moltbot health` shows “no auth configured”, go back to the wizard and set OAuth/key auth — the agent wont be able to respond without it.
Tip: `clawdbot status --all` is the best pasteable, read-only debug report.
Health probes: `clawdbot health` (or `clawdbot status --deep`) asks the running gateway for a health snapshot.
Tip: `moltbot status --all` is the best pasteable, read-only debug report.
Health probes: `moltbot health` (or `moltbot status --deep`) asks the running gateway for a health snapshot.
## Next steps (optional, but great)

View File

@@ -1,5 +1,5 @@
---
summary: "Hubs that link to every Clawdbot doc"
summary: "Hubs that link to every Moltbot doc"
read_when:
- You want a complete map of the documentation
---
@@ -18,7 +18,7 @@ Use these hubs to discover every page, including deep dives and reference docs t
- [Help](/help)
- [Configuration](/gateway/configuration)
- [Configuration examples](/gateway/configuration-examples)
- [Clawdbot assistant (Clawd)](/start/clawd)
- [Moltbot assistant (Clawd)](/start/clawd)
- [Showcase](/start/showcase)
- [Lore](/start/lore)

View File

@@ -1,5 +1,5 @@
---
summary: "First-run onboarding flow for Clawdbot (macOS app)"
summary: "First-run onboarding flow for Moltbot (macOS app)"
read_when:
- Designing the macOS onboarding assistant
- Implementing auth or identity setup
@@ -64,7 +64,7 @@ Onboarding requests TCC permissions needed for:
## 5) CLI (optional)
The app can install the global `clawdbot` CLI via npm/pnpm so terminal
The app can install the global `moltbot` CLI via npm/pnpm so terminal
workflows and launchd tasks work out of the box.
## 6) Onboarding chat (dedicated session)
@@ -75,7 +75,7 @@ from your normal conversation.
## Agent bootstrap ritual
On the first agent run, Clawdbot bootstraps a workspace (default `~/clawd`):
On the first agent run, Moltbot bootstraps a workspace (default `~/clawd`):
- Seeds `AGENTS.md`, `BOOTSTRAP.md`, `IDENTITY.md`, `USER.md`
- Runs a short Q&A ritual (one question at a time)
@@ -87,7 +87,7 @@ On the first agent run, Clawdbot bootstraps a workspace (default `~/clawd`):
Gmail Pub/Sub setup is currently a manual step. Use:
```bash
clawdbot webhooks gmail setup --account you@gmail.com
moltbot webhooks gmail setup --account you@gmail.com
```
See [/automation/gmail-pubsub](/automation/gmail-pubsub) for details.

View File

@@ -3,12 +3,12 @@ summary: "Pairing overview: approve who can DM you + which nodes can join"
read_when:
- Setting up DM access control
- Pairing a new iOS/Android node
- Reviewing Clawdbot security posture
- Reviewing Moltbot security posture
---
# Pairing
“Pairing” is Clawdbots explicit **owner approval** step.
“Pairing” is Moltbots explicit **owner approval** step.
It is used in two places:
1) **DM pairing** (who is allowed to talk to the bot)
@@ -30,8 +30,8 @@ Pairing codes:
### Approve a sender
```bash
clawdbot pairing list telegram
clawdbot pairing approve telegram <CODE>
moltbot pairing list telegram
moltbot pairing approve telegram <CODE>
```
Supported channels: `telegram`, `whatsapp`, `signal`, `imessage`, `discord`, `slack`.
@@ -53,9 +53,9 @@ creates a device pairing request that must be approved.
### Approve a node device
```bash
clawdbot devices list
clawdbot devices approve <requestId>
clawdbot devices reject <requestId>
moltbot devices list
moltbot devices approve <requestId>
moltbot devices reject <requestId>
```
### Where the state lives
@@ -66,7 +66,7 @@ Stored under `~/.clawdbot/devices/`:
### Notes
- The legacy `node.pair.*` API (CLI: `clawdbot nodes pending/approve`) is a
- The legacy `node.pair.*` API (CLI: `moltbot nodes pending/approve`) is a
separate gateway-owned pairing store. WS nodes still require device pairing.

View File

@@ -1,5 +1,5 @@
---
summary: "Setup guide: keep your Clawdbot setup tailored while staying up-to-date"
summary: "Setup guide: keep your Moltbot setup tailored while staying up-to-date"
read_when:
- Setting up a new machine
- You want “latest + greatest” without breaking your personal setup
@@ -10,7 +10,7 @@ read_when:
Last updated: 2026-01-01
## TL;DR
- **Tailoring lives outside the repo:** `~/clawd` (workspace) + `~/.clawdbot/clawdbot.json` (config).
- **Tailoring lives outside the repo:** `~/clawd` (workspace) + `~/.clawdbot/moltbot.json` (config).
- **Stable workflow:** install the macOS app; let it run the bundled Gateway.
- **Bleeding edge workflow:** run the Gateway yourself via `pnpm gateway:watch`, then let the macOS app attach in Local mode.
@@ -23,42 +23,42 @@ Last updated: 2026-01-01
If you want “100% tailored to me” *and* easy updates, keep your customization in:
- **Config:** `~/.clawdbot/clawdbot.json` (JSON/JSON5-ish)
- **Config:** `~/.clawdbot/moltbot.json` (JSON/JSON5-ish)
- **Workspace:** `~/clawd` (skills, prompts, memories; make it a private git repo)
Bootstrap once:
```bash
clawdbot setup
moltbot setup
```
From inside this repo, use the local CLI entry:
```bash
clawdbot setup
moltbot setup
```
If you dont have a global install yet, run it via `pnpm clawdbot setup`.
If you dont have a global install yet, run it via `pnpm moltbot setup`.
## Stable workflow (macOS app first)
1) Install + launch **Clawdbot.app** (menu bar).
1) Install + launch **Moltbot.app** (menu bar).
2) Complete the onboarding/permissions checklist (TCC prompts).
3) Ensure Gateway is **Local** and running (the app manages it).
4) Link surfaces (example: WhatsApp):
```bash
clawdbot channels login
moltbot channels login
```
5) Sanity check:
```bash
clawdbot health
moltbot health
```
If onboarding is not available in your build:
- Run `clawdbot setup`, then `clawdbot channels login`, then start the Gateway manually (`clawdbot gateway`).
- Run `moltbot setup`, then `moltbot channels login`, then start the Gateway manually (`moltbot gateway`).
## Bleeding edge workflow (Gateway in a terminal)
@@ -83,7 +83,7 @@ pnpm gateway:watch
### 2) Point the macOS app at your running Gateway
In **Clawdbot.app**:
In **Moltbot.app**:
- Connection Mode: **Local**
The app will attach to the running gateway on the configured port.
@@ -94,7 +94,7 @@ The app will attach to the running gateway on the configured port.
- Or via CLI:
```bash
clawdbot health
moltbot health
```
### Common footguns
@@ -102,7 +102,7 @@ clawdbot health
- **Where state lives:**
- Credentials: `~/.clawdbot/credentials/`
- Sessions: `~/.clawdbot/agents/<agentId>/sessions/`
- Logs: `/tmp/clawdbot/`
- Logs: `/tmp/moltbot/`
## Credential storage map
@@ -119,7 +119,7 @@ More detail: [Security](/gateway/security#credential-storage-map).
## Updating (without wrecking your setup)
- Keep `~/clawd` and `~/.clawdbot/` as “your stuff”; dont put personal prompts/config into the `clawdbot` repo.
- Keep `~/clawd` and `~/.clawdbot/` as “your stuff”; dont put personal prompts/config into the `moltbot` repo.
- Updating source: `git pull` + `pnpm install` (when lockfile changed) + keep using `pnpm gateway:watch`.
## Linux (systemd user service)
@@ -140,5 +140,5 @@ user service (no lingering needed). See [Gateway runbook](/gateway) for the syst
- [Gateway runbook](/gateway) (flags, supervision, ports)
- [Gateway configuration](/gateway/configuration) (config schema + examples)
- [Discord](/channels/discord) and [Telegram](/channels/telegram) (reply tags + replyToMode settings)
- [Clawdbot assistant setup](/start/clawd)
- [Moltbot assistant setup](/start/clawd)
- [macOS app](/platforms/macos) (gateway lifecycle)

View File

@@ -1,18 +1,18 @@
---
title: "Showcase"
description: "Real-world Clawdbot projects from the community"
summary: "Community-built projects and integrations powered by Clawdbot"
description: "Real-world Moltbot projects from the community"
summary: "Community-built projects and integrations powered by Moltbot"
---
# Showcase
Real projects from the community. See what people are building with Clawdbot.
Real projects from the community. See what people are building with Moltbot.
<Info>
**Want to be featured?** Share your project in [#showcase on Discord](https://discord.gg/clawd) or [tag @clawdbot on X](https://x.com/clawdbot).
**Want to be featured?** Share your project in [#showcase on Discord](https://discord.gg/clawd) or [tag @moltbot on X](https://x.com/moltbot).
</Info>
## 🎥 Clawdbot in Action
## 🎥 Moltbot in Action
Full setup walkthrough (28m) by VelvetShark.
@@ -27,7 +27,7 @@ Full setup walkthrough (28m) by VelvetShark.
>
<iframe
src="https://www.youtube-nocookie.com/embed/SaWSPZoPX34"
title="Clawdbot: The self-hosted AI that Siri should have been (Full setup)"
title="Moltbot: The self-hosted AI that Siri should have been (Full setup)"
style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%" }}
frameBorder="0"
loading="lazy"
@@ -49,7 +49,7 @@ Full setup walkthrough (28m) by VelvetShark.
>
<iframe
src="https://www.youtube-nocookie.com/embed/mMSKQvlmFuQ"
title="Clawdbot showcase video"
title="Moltbot showcase video"
style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%" }}
frameBorder="0"
loading="lazy"
@@ -71,7 +71,7 @@ Full setup walkthrough (28m) by VelvetShark.
>
<iframe
src="https://www.youtube-nocookie.com/embed/5kkIJNUGFho"
title="Clawdbot community showcase"
title="Moltbot community showcase"
style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%" }}
frameBorder="0"
loading="lazy"
@@ -89,17 +89,17 @@ Full setup walkthrough (28m) by VelvetShark.
<Card title="PR Review → Telegram Feedback" icon="code-pull-request" href="https://x.com/i/status/2010878524543131691">
**@bangnokia** • `review` `github` `telegram`
OpenCode finishes the change → opens a PR → Clawdbot reviews the diff and replies in Telegram with “minor suggestions” plus a clear merge verdict (including critical fixes to apply first).
OpenCode finishes the change → opens a PR → Moltbot reviews the diff and replies in Telegram with “minor suggestions” plus a clear merge verdict (including critical fixes to apply first).
<img src="/assets/showcase/pr-review-telegram.jpg" alt="Clawdbot PR review feedback delivered in Telegram" />
<img src="/assets/showcase/pr-review-telegram.jpg" alt="Moltbot PR review feedback delivered in Telegram" />
</Card>
<Card title="Wine Cellar Skill in Minutes" icon="wine-glass" href="https://x.com/i/status/2010916352454791216">
**@prades_maxime** • `skills` `local` `csv`
Asked “Robby” (@clawdbot) for a local wine cellar skill. It requests a sample CSV export + where to store it, then builds/tests the skill fast (962 bottles in the example).
Asked “Robby” (@moltbot) for a local wine cellar skill. It requests a sample CSV export + where to store it, then builds/tests the skill fast (962 bottles in the example).
<img src="/assets/showcase/wine-cellar-skill.jpg" alt="Clawdbot building a local wine cellar skill from CSV" />
<img src="/assets/showcase/wine-cellar-skill.jpg" alt="Moltbot building a local wine cellar skill from CSV" />
</Card>
<Card title="Tesco Shop Autopilot" icon="cart-shopping" href="https://x.com/i/status/2009724862470689131">
@@ -121,7 +121,7 @@ Full setup walkthrough (28m) by VelvetShark.
<Card title="Agents UI" icon="window-maximize" href="https://releaseflow.net/kitze/agents-ui">
**@kitze** • `ui` `skills` `sync`
Desktop app to manage skills/commands across Agents, Claude, Codex, and Clawdbot.
Desktop app to manage skills/commands across Agents, Claude, Codex, and Moltbot.
<img src="/assets/showcase/agents-ui.jpg" alt="Agents UI app" />
</Card>
@@ -167,7 +167,7 @@ Full setup walkthrough (28m) by VelvetShark.
<Card title="R2 Upload (Send Me My Files)" icon="cloud-arrow-up" href="https://clawdhub.com/skills/r2-upload">
**@julianengel** • `files` `r2` `presigned-urls`
Upload to Cloudflare R2/S3 and generate secure presigned download links. Perfect for remote Clawdbot instances.
Upload to Cloudflare R2/S3 and generate secure presigned download links. Perfect for remote Moltbot instances.
</Card>
<Card title="iOS App via Telegram" icon="mobile" href="#">
@@ -194,7 +194,7 @@ Full setup walkthrough (28m) by VelvetShark.
<Card title="Linear CLI" icon="terminal" href="https://github.com/Finesssee/linear-cli">
**@NessZerra** • `devtools` `linear` `cli` `issues`
CLI for Linear that integrates with agentic workflows (Claude Code, Clawdbot). Manage issues, projects, and workflows from the terminal. First external PR merged!
CLI for Linear that integrates with agentic workflows (Claude Code, Moltbot). Manage issues, projects, and workflows from the terminal. First external PR merged!
</Card>
<Card title="Beeper CLI" icon="message" href="https://github.com/blqke/beepcli">
@@ -212,23 +212,23 @@ Full setup walkthrough (28m) by VelvetShark.
<Card title="Winix Air Purifier Control" icon="wind" href="https://x.com/antonplex/status/2010518442471006253">
**@antonplex** • `automation` `hardware` `air-quality`
Claude Code discovered and confirmed the purifier controls, then Clawdbot takes over to manage room air quality.
Claude Code discovered and confirmed the purifier controls, then Moltbot takes over to manage room air quality.
<img src="/assets/showcase/winix-air-purifier.jpg" alt="Winix air purifier control via Clawdbot" />
<img src="/assets/showcase/winix-air-purifier.jpg" alt="Winix air purifier control via Moltbot" />
</Card>
<Card title="Pretty Sky Camera Shots" icon="camera" href="https://x.com/signalgaining/status/2010523120604746151">
**@signalgaining** • `automation` `camera` `skill` `images`
Triggered by a roof camera: ask Clawdbot to snap a sky photo whenever it looks pretty — it designed a skill and took the shot.
Triggered by a roof camera: ask Moltbot to snap a sky photo whenever it looks pretty — it designed a skill and took the shot.
<img src="/assets/showcase/roof-camera-sky.jpg" alt="Roof camera sky snapshot captured by Clawdbot" />
<img src="/assets/showcase/roof-camera-sky.jpg" alt="Roof camera sky snapshot captured by Moltbot" />
</Card>
<Card title="Visual Morning Briefing Scene" icon="robot" href="https://x.com/buddyhadry/status/2010005331925954739">
**@buddyhadry** • `automation` `briefing` `images` `telegram`
A scheduled prompt generates a single "scene" image each morning (weather, tasks, date, favorite post/quote) via a Clawdbot persona.
A scheduled prompt generates a single "scene" image each morning (weather, tasks, date, favorite post/quote) via a Moltbot persona.
</Card>
<Card title="Padel Court Booking" icon="calendar-check" href="https://github.com/joshp123/padel-cli">
@@ -260,13 +260,13 @@ Full setup walkthrough (28m) by VelvetShark.
<Card title="Jira Skill Builder" icon="diagram-project" href="https://x.com/jdrhyne/status/2008336434827002232">
**@jdrhyne** • `automation` `jira` `skill` `devtools`
Clawdbot connected to Jira, then generated a new skill on the fly (before it existed on ClawdHub).
Moltbot connected to Jira, then generated a new skill on the fly (before it existed on ClawdHub).
</Card>
<Card title="Todoist Skill via Telegram" icon="list-check" href="https://x.com/iamsubhrajyoti/status/2009949389884920153">
**@iamsubhrajyoti** • `automation` `todoist` `skill` `telegram`
Automated Todoist tasks and had Clawdbot generate the skill directly in Telegram chat.
Automated Todoist tasks and had Moltbot generate the skill directly in Telegram chat.
</Card>
<Card title="TradingView Analysis" icon="chart-line">
@@ -290,7 +290,7 @@ Full setup walkthrough (28m) by VelvetShark.
<Card title="xuezh Chinese Learning" icon="language" href="https://github.com/joshp123/xuezh">
**@joshp123** • `learning` `voice` `skill`
Chinese learning engine with pronunciation feedback and study flows via Clawdbot.
Chinese learning engine with pronunciation feedback and study flows via Moltbot.
<img src="/assets/showcase/xuezh-pronunciation.jpeg" alt="xuezh pronunciation feedback" />
</Card>
@@ -322,7 +322,7 @@ Full setup walkthrough (28m) by VelvetShark.
<Card title="Clawdia Phone Bridge" icon="phone" href="https://github.com/alejandroOPI/clawdia-bridge">
**@alejandroOPI** • `voice` `vapi` `bridge`
Vapi voice assistant ↔ Clawdbot HTTP bridge. Near real-time phone calls with your agent.
Vapi voice assistant ↔ Moltbot HTTP bridge. Near real-time phone calls with your agent.
</Card>
<Card title="OpenRouter Transcription" icon="microphone" href="https://clawdhub.com/obviyus/openrouter-transcribe">
@@ -337,10 +337,10 @@ Full setup walkthrough (28m) by VelvetShark.
<CardGroup cols={2}>
<Card title="Home Assistant Add-on" icon="home" href="https://github.com/ngutman/clawdbot-ha-addon">
<Card title="Home Assistant Add-on" icon="home" href="https://github.com/ngutman/moltbot-ha-addon">
**@ngutman** • `homeassistant` `docker` `raspberry-pi`
Clawdbot gateway running on Home Assistant OS with SSH tunnel support and persistent state.
Moltbot gateway running on Home Assistant OS with SSH tunnel support and persistent state.
</Card>
<Card title="Home Assistant Skill" icon="toggle-on" href="https://clawdhub.com/skills/homeassistant">
@@ -349,10 +349,10 @@ Full setup walkthrough (28m) by VelvetShark.
Control and automate Home Assistant devices via natural language.
</Card>
<Card title="Nix Packaging" icon="snowflake" href="https://github.com/clawdbot/nix-clawdbot">
**@clawdbot** • `nix` `packaging` `deployment`
<Card title="Nix Packaging" icon="snowflake" href="https://github.com/moltbot/nix-moltbot">
**@moltbot** • `nix` `packaging` `deployment`
Batteries-included nixified Clawdbot configuration for reproducible deployments.
Batteries-included nixified Moltbot configuration for reproducible deployments.
</Card>
<Card title="CalDAV Calendar" icon="calendar" href="https://clawdhub.com/skills/caldav-calendar">
@@ -370,7 +370,7 @@ Full setup walkthrough (28m) by VelvetShark.
<Card title="GoHome Automation" icon="house-signal" href="https://github.com/joshp123/gohome">
**@joshp123** • `home` `nix` `grafana`
Nix-native home automation with Clawdbot as the interface, plus beautiful Grafana dashboards.
Nix-native home automation with Moltbot as the interface, plus beautiful Grafana dashboards.
<img src="/assets/showcase/gohome-grafana.png" alt="GoHome Grafana dashboard" />
</Card>
@@ -392,7 +392,7 @@ Full setup walkthrough (28m) by VelvetShark.
<Card title="StarSwap Marketplace" icon="star" href="https://star-swap.com/">
**Community**`marketplace` `astronomy` `webapp`
Full astronomy gear marketplace. Built with/around the Clawdbot ecosystem.
Full astronomy gear marketplace. Built with/around the Moltbot ecosystem.
</Card>
</CardGroup>
@@ -405,7 +405,7 @@ Have something to share? We'd love to feature it!
<Steps>
<Step title="Share It">
Post in [#showcase on Discord](https://discord.gg/clawd) or [tweet @clawdbot](https://x.com/clawdbot)
Post in [#showcase on Discord](https://discord.gg/clawd) or [tweet @moltbot](https://x.com/moltbot)
</Step>
<Step title="Include Details">
Tell us what it does, link to the repo/demo, share a screenshot if you have one

View File

@@ -7,7 +7,7 @@ read_when:
# Onboarding Wizard (CLI)
The onboarding wizard is the **recommended** way to set up Clawdbot on macOS,
The onboarding wizard is the **recommended** way to set up Moltbot on macOS,
Linux, or Windows (via WSL2; strongly recommended).
It configures a local Gateway or a remote Gateway connection, plus channels, skills,
and workspace defaults in one guided flow.
@@ -15,20 +15,20 @@ and workspace defaults in one guided flow.
Primary entrypoint:
```bash
clawdbot onboard
moltbot onboard
```
Fastest first chat: open the Control UI (no channel setup needed). Run
`clawdbot dashboard` and chat in the browser. Docs: [Dashboard](/web/dashboard).
`moltbot dashboard` and chat in the browser. Docs: [Dashboard](/web/dashboard).
Followup reconfiguration:
```bash
clawdbot configure
moltbot configure
```
Recommended: set up a Brave Search API key so the agent can use `web_search`
(`web_fetch` works without a key). Easiest path: `clawdbot configure --section web`
(`web_fetch` works without a key). Easiest path: `moltbot configure --section web`
which stores `tools.web.search.apiKey`. Docs: [Web tools](/tools/web).
## QuickStart vs Advanced
@@ -62,7 +62,7 @@ It does **not** install or change anything on the remote host.
To add more isolated agents (separate workspace + sessions + auth), use:
```bash
clawdbot agents add <name>
moltbot agents add <name>
```
Tip: `--json` does **not** imply non-interactive mode. Use `--non-interactive` (and `--workspace`) for scripts.
@@ -70,11 +70,11 @@ Tip: `--json` does **not** imply non-interactive mode. Use `--non-interactive` (
## Flow details (local)
1) **Existing config detection**
- If `~/.clawdbot/clawdbot.json` exists, choose **Keep / Modify / Reset**.
- If `~/.clawdbot/moltbot.json` exists, choose **Keep / Modify / Reset**.
- Re-running the wizard does **not** wipe anything unless you explicitly choose **Reset**
(or pass `--reset`).
- If the config is invalid or contains legacy keys, the wizard stops and asks
you to run `clawdbot doctor` before continuing.
you to run `moltbot doctor` before continuing.
- Reset uses `trash` (never `rm`) and offers scopes:
- Config only
- Config + credentials + sessions
@@ -124,7 +124,7 @@ Tip: `--json` does **not** imply non-interactive mode. Use `--non-interactive` (
- Mattermost (plugin): bot token + base URL.
- Signal: optional `signal-cli` install + account config.
- iMessage: local `imsg` CLI path + DB access.
- DM security: default is pairing. First DM sends a code; approve via `clawdbot pairing approve <channel> <code>` or use allowlists.
- DM security: default is pairing. First DM sends a code; approve via `moltbot pairing approve <channel> <code>` or use allowlists.
6) **Daemon install**
- macOS: LaunchAgent
@@ -135,8 +135,8 @@ Tip: `--json` does **not** imply non-interactive mode. Use `--non-interactive` (
- **Runtime selection:** Node (recommended; required for WhatsApp/Telegram). Bun is **not recommended**.
7) **Health check**
- Starts the Gateway (if needed) and runs `clawdbot health`.
- Tip: `clawdbot status --deep` adds gateway health probes to status output (requires a reachable gateway).
- Starts the Gateway (if needed) and runs `moltbot health`.
- Tip: `moltbot status --deep` adds gateway health probes to status output (requires a reachable gateway).
8) **Skills (recommended)**
- Reads the available skills and checks requirements.
@@ -165,7 +165,7 @@ Notes:
## Add another agent
Use `clawdbot agents add <name>` to create a separate agent with its own workspace,
Use `moltbot agents add <name>` to create a separate agent with its own workspace,
sessions, and auth profiles. Running without `--workspace` launches the wizard.
What it sets:
@@ -183,7 +183,7 @@ Notes:
Use `--non-interactive` to automate or script onboarding:
```bash
clawdbot onboard --non-interactive \
moltbot onboard --non-interactive \
--mode local \
--auth-choice apiKey \
--anthropic-api-key "$ANTHROPIC_API_KEY" \
@@ -199,7 +199,7 @@ Add `--json` for a machinereadable summary.
Gemini example:
```bash
clawdbot onboard --non-interactive \
moltbot onboard --non-interactive \
--mode local \
--auth-choice gemini-api-key \
--gemini-api-key "$GEMINI_API_KEY" \
@@ -210,7 +210,7 @@ clawdbot onboard --non-interactive \
Z.AI example:
```bash
clawdbot onboard --non-interactive \
moltbot onboard --non-interactive \
--mode local \
--auth-choice zai-api-key \
--zai-api-key "$ZAI_API_KEY" \
@@ -221,7 +221,7 @@ clawdbot onboard --non-interactive \
Vercel AI Gateway example:
```bash
clawdbot onboard --non-interactive \
moltbot onboard --non-interactive \
--mode local \
--auth-choice ai-gateway-api-key \
--ai-gateway-api-key "$AI_GATEWAY_API_KEY" \
@@ -232,7 +232,7 @@ clawdbot onboard --non-interactive \
Moonshot example:
```bash
clawdbot onboard --non-interactive \
moltbot onboard --non-interactive \
--mode local \
--auth-choice moonshot-api-key \
--moonshot-api-key "$MOONSHOT_API_KEY" \
@@ -243,7 +243,7 @@ clawdbot onboard --non-interactive \
Synthetic example:
```bash
clawdbot onboard --non-interactive \
moltbot onboard --non-interactive \
--mode local \
--auth-choice synthetic-api-key \
--synthetic-api-key "$SYNTHETIC_API_KEY" \
@@ -254,7 +254,7 @@ clawdbot onboard --non-interactive \
OpenCode Zen example:
```bash
clawdbot onboard --non-interactive \
moltbot onboard --non-interactive \
--mode local \
--auth-choice opencode-zen \
--opencode-zen-api-key "$OPENCODE_API_KEY" \
@@ -265,7 +265,7 @@ clawdbot onboard --non-interactive \
Add agent (noninteractive) example:
```bash
clawdbot agents add work \
moltbot agents add work \
--workspace ~/clawd-work \
--model openai/gpt-5.2 \
--bind whatsapp:biz \
@@ -292,7 +292,7 @@ Notes:
## What the wizard writes
Typical fields in `~/.clawdbot/clawdbot.json`:
Typical fields in `~/.clawdbot/moltbot.json`:
- `agents.defaults.workspace`
- `agents.defaults.model` / `models.providers` (if Minimax chosen)
- `gateway.*` (mode, bind, auth, tailscale)
@@ -305,7 +305,7 @@ Typical fields in `~/.clawdbot/clawdbot.json`:
- `wizard.lastRunCommand`
- `wizard.lastRunMode`
`clawdbot agents add` writes `agents.list[]` and optional `bindings`.
`moltbot agents add` writes `agents.list[]` and optional `bindings`.
WhatsApp credentials go under `~/.clawdbot/credentials/whatsapp/<accountId>/`.
Sessions are stored under `~/.clawdbot/agents/<agentId>/sessions/`.