docs: clarify moltbot/clawdbot CLI naming fallback

Fixes #3038

Users hit "command not found: moltbot" after install because docs only
reference `moltbot`, but package.json defines both `moltbot` and `clawdbot`
bins. Some install methods may expose only `clawdbot`.

Changes:
- Add "try clawdbot (compatibility shim)" fallback in 7 key docs
- README, install docs, getting started, troubleshooting
- Consistent messaging: try clawdbot first → then check PATH
- All links follow Mintlify root-relative convention

Reviewed-by: Codex (threadId: 019c0332-8694-7531-b987-a6f795e1a668)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2026-01-28 14:08:50 +08:00

2.6 KiB

Raw Blame History

summary

read_when

Troubleshooting hub: symptoms → checks → fixes

You see an error and want the fix path

The installer says “success” but the CLI doesn’t work

Troubleshooting

First 60 seconds

Run these in order:

moltbot status
moltbot status --all
moltbot gateway probe
moltbot logs --follow
moltbot doctor

If the gateway is reachable, deep probes:

moltbot status --deep

Common “it broke” cases

`moltbot: command not found`

First try clawdbot (compatibility shim). If that also fails, it's almost always a Node/npm PATH issue. Start here:

Install (Node/npm PATH sanity)

Installer fails (or you need full logs)

Re-run the installer in verbose mode to see the full trace and npm output:

curl -fsSL https://molt.bot/install.sh | bash -s -- --verbose

For beta installs:

curl -fsSL https://molt.bot/install.sh | bash -s -- --beta --verbose

You can also set CLAWDBOT_VERBOSE=1 instead of the flag.

Gateway “unauthorized”, can’t connect, or keeps reconnecting

Control UI fails on HTTP (device identity required)

`docs.molt.bot` shows an SSL error (Comcast/Xfinity)

Some Comcast/Xfinity connections block docs.molt.bot via Xfinity Advanced Security. Disable Advanced Security or add docs.molt.bot to the allowlist, then retry.

Xfinity Advanced Security help: https://www.xfinity.com/support/articles/using-xfinity-xfi-advanced-security
Quick sanity checks: try a mobile hotspot or VPN to confirm it’s ISP-level filtering

Service says running, but RPC probe fails

Model/auth failures (rate limit, billing, “all models failed”)

`/model` says `model not allowed`

This usually means agents.defaults.models is configured as an allowlist. When it’s non-empty, only those provider/model keys can be selected.

Check the allowlist: moltbot config get agents.defaults.models
Add the model you want (or clear the allowlist) and retry /model
Use /models to browse the allowed providers/models

When filing an issue

Paste a safe report:

moltbot status --all

If you can, include the relevant log tail from moltbot logs --follow.

2.6 KiB Raw Blame History Unescape Escape