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,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)