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

@@ -6,7 +6,7 @@ read_when:
---
# Authentication
Clawdbot supports OAuth and API keys for model providers. For Anthropic
Moltbot supports OAuth and API keys for model providers. For Anthropic
accounts, we recommend using an **API key**. For Claude subscription access,
use the longlived token created by `claude setup-token`.
@@ -18,11 +18,11 @@ layout.
If youre using Anthropic directly, use an API key.
1) Create an API key in the Anthropic Console.
2) Put it on the **gateway host** (the machine running `clawdbot gateway`).
2) Put it on the **gateway host** (the machine running `moltbot gateway`).
```bash
export ANTHROPIC_API_KEY="..."
clawdbot models status
moltbot models status
```
3) If the Gateway runs under systemd/launchd, prefer putting the key in
@@ -37,12 +37,12 @@ EOF
Then restart the daemon (or restart your Gateway process) and re-check:
```bash
clawdbot models status
clawdbot doctor
moltbot models status
moltbot doctor
```
If youd rather not manage env vars yourself, the onboarding wizard can store
API keys for daemon use: `clawdbot onboard`.
API keys for daemon use: `moltbot onboard`.
See [Help](/help) for details on env inheritance (`env.shellEnv`,
`~/.clawdbot/.env`, systemd/launchd).
@@ -56,16 +56,16 @@ subscription, the setup-token flow is also supported. Run it on the **gateway ho
claude setup-token
```
Then paste it into Clawdbot:
Then paste it into Moltbot:
```bash
clawdbot models auth setup-token --provider anthropic
moltbot models auth setup-token --provider anthropic
```
If the token was created on another machine, paste it manually:
```bash
clawdbot models auth paste-token --provider anthropic
moltbot models auth paste-token --provider anthropic
```
If you see an Anthropic error like:
@@ -79,14 +79,14 @@ This credential is only authorized for use with Claude Code and cannot be used f
Manual token entry (any provider; writes `auth-profiles.json` + updates config):
```bash
clawdbot models auth paste-token --provider anthropic
clawdbot models auth paste-token --provider openrouter
moltbot models auth paste-token --provider anthropic
moltbot models auth paste-token --provider openrouter
```
Automation-friendly check (exit `1` when expired/missing, `2` when expiring):
```bash
clawdbot models status --check
moltbot models status --check
```
Optional ops scripts (systemd/Termux) are documented here:
@@ -97,8 +97,8 @@ Optional ops scripts (systemd/Termux) are documented here:
## Checking model auth status
```bash
clawdbot models status
clawdbot doctor
moltbot models status
moltbot doctor
```
## Controlling which credential is used
@@ -114,9 +114,9 @@ Use `/model` (or `/model list`) for a compact picker; use `/model status` for th
Set an explicit auth profile order override for an agent (stored in that agents `auth-profiles.json`):
```bash
clawdbot models auth order get --provider anthropic
clawdbot models auth order set --provider anthropic anthropic:default
clawdbot models auth order clear --provider anthropic
moltbot models auth order get --provider anthropic
moltbot models auth order set --provider anthropic anthropic:default
moltbot models auth order clear --provider anthropic
```
Use `--agent <id>` to target a specific agent; omit it to use the configured default agent.
@@ -129,12 +129,12 @@ If the Anthropic token profile is missing, run `claude setup-token` on the
**gateway host**, then re-check:
```bash
clawdbot models status
moltbot models status
```
### Token expiring/expired
Run `clawdbot models status` to confirm which profile is expiring. If the profile
Run `moltbot models status` to confirm which profile is expiring. If the profile
is missing, rerun `claude setup-token` and paste the token again.
## Requirements