let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: update molt.bot domains

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-27 11:27:41 +00:00
parent f4004054ab
commit 83460df96f
137 changed files with 653 additions and 538 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/install/index.md
View File

@@ -12,13 +12,13 @@ Use the installer unless you have a reason not to. It sets up the CLI and runs o
## Quick install (recommended)
```bash
curl -fsSL https://clawd.bot/install.sh | bash
curl -fsSL https://molt.bot/install.sh | bash
```
Windows (PowerShell):
```powershell
iwr -useb https://clawd.bot/install.ps1 | iex
iwr -useb https://molt.bot/install.ps1 | iex
```
Next step (if you skipped onboarding):
@@ -40,13 +40,13 @@ clawdbot onboard --install-daemon
Installs `clawdbot` globally via npm and runs onboarding.
```bash
curl -fsSL https://clawd.bot/install.sh | bash
curl -fsSL https://molt.bot/install.sh | bash
```
Installer flags:
```bash
curl -fsSL https://clawd.bot/install.sh | bash -s -- --help
curl -fsSL https://molt.bot/install.sh | bash -s -- --help
```
Details: [Installer internals](/install/installer).
@@ -54,7 +54,7 @@ Details: [Installer internals](/install/installer).
Non-interactive (skip onboarding):
```bash
curl -fsSL https://clawd.bot/install.sh | bash -s -- --no-onboard
curl -fsSL https://molt.bot/install.sh | bash -s -- --no-onboard
```
### 2) Global install (manual)
@@ -123,10 +123,10 @@ The installer supports two methods:
```bash
# Explicit npm
curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method npm
curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method npm
# Install from GitHub (source checkout)
curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git
curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git
```
Common flags:

24
docs/install/installer.md
View File

@@ -1,29 +1,29 @@
---
summary: "How the installer scripts work (install.sh + install-cli.sh), flags, and automation"
read_when:
- You want to understand `clawd.bot/install.sh`
- You want to understand `molt.bot/install.sh`
- You want to automate installs (CI / headless)
- You want to install from a GitHub checkout
---
# Installer internals
Clawdbot ships two installer scripts (served from `clawd.bot`):
Clawdbot ships two installer scripts (served from `molt.bot`):
- `https://clawd.bot/install.sh` — “recommended” installer (global npm install by default; can also install from a GitHub checkout)
- `https://clawd.bot/install-cli.sh` — non-root-friendly CLI installer (installs into a prefix with its own Node)
- `https://clawd.bot/install.ps1` — Windows PowerShell installer (npm by default; optional git install)
- `https://molt.bot/install.sh` — “recommended” installer (global npm install by default; can also install from a GitHub checkout)
- `https://molt.bot/install-cli.sh` — non-root-friendly CLI installer (installs into a prefix with its own Node)
- `https://molt.bot/install.ps1` — Windows PowerShell installer (npm by default; optional git install)
To see the current flags/behavior, run:
```bash
curl -fsSL https://clawd.bot/install.sh | bash -s -- --help
curl -fsSL https://molt.bot/install.sh | bash -s -- --help
```
Windows (PowerShell) help:
```powershell
& ([scriptblock]::Create((iwr -useb https://clawd.bot/install.ps1))) -?
& ([scriptblock]::Create((iwr -useb https://molt.bot/install.ps1))) -?
```
If the installer completes but `clawdbot` is not found in a new terminal, it’s usually a Node/npm PATH issue. See: [Install](/install#nodejs--npm-path-sanity).
@@ -45,7 +45,7 @@ What it does (high level):
If you *want* `sharp` to link against a globally-installed libvips (or you’re debugging), set:
```bash
SHARP_IGNORE_GLOBAL_LIBVIPS=0 curl -fsSL https://clawd.bot/install.sh | bash
SHARP_IGNORE_GLOBAL_LIBVIPS=0 curl -fsSL https://molt.bot/install.sh | bash
```
### Discoverability / “git install” prompt
@@ -78,7 +78,7 @@ This script installs `clawdbot` into a prefix (default: `~/.clawdbot`) and also
Help:
```bash
curl -fsSL https://clawd.bot/install-cli.sh | bash -s -- --help
curl -fsSL https://molt.bot/install-cli.sh | bash -s -- --help
```
## install.ps1 (Windows PowerShell)
@@ -94,15 +94,15 @@ What it does (high level):
Examples:
```powershell
iwr -useb https://clawd.bot/install.ps1 | iex
iwr -useb https://molt.bot/install.ps1 | iex
```
```powershell
iwr -useb https://clawd.bot/install.ps1 | iex -InstallMethod git
iwr -useb https://molt.bot/install.ps1 | iex -InstallMethod git
```
```powershell
iwr -useb https://clawd.bot/install.ps1 | iex -InstallMethod git -GitDir "C:\\clawdbot"
iwr -useb https://molt.bot/install.ps1 | iex -InstallMethod git -GitDir "C:\\clawdbot"
```
Environment variables:

2
docs/install/uninstall.md
View File

@@ -113,7 +113,7 @@ If you used a profile, delete the matching task name and `~\.clawdbot-<profile>\
### Normal install (install.sh / npm / pnpm / bun)
If you used `https://clawd.bot/install.sh` or `install.ps1`, the CLI was installed with `npm install -g clawdbot@latest`.
If you used `https://molt.bot/install.sh` or `install.ps1`, the CLI was installed with `npm install -g clawdbot@latest`.
Remove it with `npm rm -g clawdbot` (or `pnpm remove -g` / `bun remove -g` if you installed that way).
### Source checkout (git clone)

87
docs/install/updating.md
View File

@@ -1,32 +1,33 @@
---
summary: "Updating Clawdbot safely (global install or source), plus rollback strategy"
summary: "Updating Moltbot safely (global install or source), plus rollback strategy"
read_when:
- Updating Clawdbot
- Updating Moltbot
- Something breaks after an update
---
# Updating
Clawdbot is moving fast (pre “1.0”). Treat updates like shipping infra: update → run checks → restart (or use `clawdbot update`, which restarts) → verify.
Moltbot is moving fast (pre “1.0”). Treat updates like shipping infra: update → run checks → restart (or use `moltbot update`, which restarts) → verify.
## Recommended: re-run the website installer (upgrade in place)
The **preferred** update path is to re-run the installer from the website. It
detects existing installs, upgrades in place, and runs `clawdbot doctor` when
detects existing installs, upgrades in place, and runs `moltbot doctor` when
needed.
```bash
curl -fsSL https://clawd.bot/install.sh | bash
curl -fsSL https://molt.bot/install.sh | bash
```
Notes:
- Add `--no-onboard` if you don’t want the onboarding wizard to run again.
- For **source installs**, use:
```bash
curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git --no-onboard
curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git --no-onboard
```
The installer will `git pull --rebase` **only** if the repo is clean.
- For **global installs**, the script uses `npm install -g clawdbot@latest` under the hood.
- For **global installs**, the script uses `npm install -g moltbot@latest` under the hood.
- Legacy note: `clawdbot` remains available as a compatibility shim.
## Before you update
@@ -42,20 +43,20 @@ Notes:
Global install (pick one):
```bash
npm i -g clawdbot@latest
npm i -g moltbot@latest
```
```bash
pnpm add -g clawdbot@latest
pnpm add -g moltbot@latest
```
We do **not** recommend Bun for the Gateway runtime (WhatsApp/Telegram bugs).
To switch update channels (git + npm installs):
```bash
clawdbot update --channel beta
clawdbot update --channel dev
clawdbot update --channel stable
moltbot update --channel beta
moltbot update --channel dev
moltbot update --channel stable
```
Use `--tag <dist-tag|version>` for a one-off install tag/version.
@@ -67,36 +68,36 @@ Note: on npm installs, the gateway logs an update hint on startup (checks the cu
Then:
```bash
clawdbot doctor
clawdbot gateway restart
clawdbot health
moltbot doctor
moltbot gateway restart
moltbot health
```
Notes:
- If your Gateway runs as a service, `clawdbot gateway restart` is preferred over killing PIDs.
- If your Gateway runs as a service, `moltbot gateway restart` is preferred over killing PIDs.
- If you’re pinned to a specific version, see “Rollback / pinning” below.
## Update (`clawdbot update`)
## Update (`moltbot update`)
For **source installs** (git checkout), prefer:
```bash
clawdbot update
moltbot update
```
It runs a safe-ish update flow:
- Requires a clean worktree.
- Switches to the selected channel (tag or branch).
- Fetches + rebases against the configured upstream (dev channel).
- Installs deps, builds, builds the Control UI, and runs `clawdbot doctor`.
- Installs deps, builds, builds the Control UI, and runs `moltbot doctor`.
- Restarts the gateway by default (use `--no-restart` to skip).
If you installed via **npm/pnpm** (no git metadata), `clawdbot update` will try to update via your package manager. If it can’t detect the install, use “Update (global install)” instead.
If you installed via **npm/pnpm** (no git metadata), `moltbot update` will try to update via your package manager. If it can’t detect the install, use “Update (global install)” instead.
## Update (Control UI / RPC)
The Control UI has **Update & Restart** (RPC: `update.run`). It:
1) Runs the same source-update flow as `clawdbot update` (git checkout only).
1) Runs the same source-update flow as `moltbot update` (git checkout only).
2) Writes a restart sentinel with a structured report (stdout/stderr tail).
3) Restarts the gateway and pings the last active session with the report.
@@ -109,7 +110,7 @@ From the repo checkout:
Preferred:
```bash
clawdbot update
moltbot update
```
Manual (equivalent-ish):
@@ -119,21 +120,21 @@ git pull
pnpm install
pnpm build
pnpm ui:build # auto-installs UI deps on first run
clawdbot doctor
clawdbot health
moltbot doctor
moltbot health
```
Notes:
- `pnpm build` matters when you run the packaged `clawdbot` binary ([`dist/entry.js`](https://github.com/clawdbot/clawdbot/blob/main/dist/entry.js)) or use Node to run `dist/`.
- If you run from a repo checkout without a global install, use `pnpm clawdbot ...` for CLI commands.
- If you run directly from TypeScript (`pnpm clawdbot ...`), a rebuild is usually unnecessary, but **config migrations still apply** → run doctor.
- Switching between global and git installs is easy: install the other flavor, then run `clawdbot doctor` so the gateway service entrypoint is rewritten to the current install.
- `pnpm build` matters when you run the packaged `moltbot` binary ([`dist/entry.js`](https://github.com/clawdbot/clawdbot/blob/main/dist/entry.js)) or use Node to run `dist/`.
- If you run from a repo checkout without a global install, use `pnpm moltbot ...` for CLI commands.
- If you run directly from TypeScript (`pnpm moltbot ...`), a rebuild is usually unnecessary, but **config migrations still apply** → run doctor.
- Switching between global and git installs is easy: install the other flavor, then run `moltbot doctor` so the gateway service entrypoint is rewritten to the current install.
## Always run: `clawdbot doctor`
## Always Run: `moltbot doctor`
Doctor is the “safe update” command. It’s intentionally boring: repair + migrate + warn.
Note: if you’re on a **source install** (git checkout), `clawdbot doctor` will offer to run `clawdbot update` first.
Note: if you’re on a **source install** (git checkout), `moltbot doctor` will offer to run `moltbot update` first.
Typical things it does:
- Migrate deprecated config keys / legacy config file locations.
@@ -149,18 +150,18 @@ Details: [Doctor](/gateway/doctor)
CLI (works regardless of OS):
```bash
clawdbot gateway status
clawdbot gateway stop
clawdbot gateway restart
clawdbot gateway --port 18789
clawdbot logs --follow
moltbot gateway status
moltbot gateway stop
moltbot gateway restart
moltbot gateway --port 18789
moltbot logs --follow
```
If you’re supervised:
- macOS launchd (app-bundled LaunchAgent): `launchctl kickstart -k gui/$UID/com.clawdbot.gateway` (use `com.clawdbot.<profile>` if set)
- Linux systemd user service: `systemctl --user restart clawdbot-gateway[-<profile>].service`
- Windows (WSL2): `systemctl --user restart clawdbot-gateway[-<profile>].service`
- `launchctl`/`systemctl` only work if the service is installed; otherwise run `clawdbot gateway install`.
- `launchctl`/`systemctl` only work if the service is installed; otherwise run `moltbot gateway install`.
Runbook + exact service labels: [Gateway runbook](/gateway)
@@ -171,20 +172,20 @@ Runbook + exact service labels: [Gateway runbook](/gateway)
Install a known-good version (replace `<version>` with the last working one):
```bash
npm i -g clawdbot@<version>
npm i -g moltbot@<version>
```
```bash
pnpm add -g clawdbot@<version>
pnpm add -g moltbot@<version>
```
Tip: to see the current published version, run `npm view clawdbot version`.
Tip: to see the current published version, run `npm view moltbot version`.
Then restart + re-run doctor:
```bash
clawdbot doctor
clawdbot gateway restart
moltbot doctor
moltbot gateway restart
```
### Pin (source) by date
@@ -201,7 +202,7 @@ Then reinstall deps + restart:
```bash
pnpm install
pnpm build
clawdbot gateway restart
moltbot gateway restart
```
If you want to go back to latest later:
@@ -213,6 +214,6 @@ git pull
## If you’re stuck
- Run `clawdbot doctor` again and read the output carefully (it often tells you the fix).
- Run `moltbot doctor` again and read the output carefully (it often tells you the fix).
- Check: [Troubleshooting](/gateway/troubleshooting)
- Ask in Discord: https://channels.discord.gg/clawd