LLM/moltbot
1
0
Fork 0
mirror of https://github.com/moltbot/moltbot.git synced 2026-03-07 22:44:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

refactor: rename to openclaw

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-30 03:15:10 +01:00
parent 4583f88626
commit 9a7160786a
2357 changed files with 16688 additions and 16788 deletions
Download Patch File Download Diff File Expand all files Collapse all files

676
docs/help/faq.md
View File

File diff suppressed because it is too large Load Diff

32
docs/help/troubleshooting.md
View File

@@ -12,22 +12,22 @@ read_when:
Run these in order:
```bash
moltbot status
moltbot status --all
moltbot gateway probe
moltbot logs --follow
moltbot doctor
openclaw status
openclaw status --all
openclaw gateway probe
openclaw logs --follow
openclaw doctor
```
If the gateway is reachable, deep probes:
```bash
moltbot status --deep
openclaw status --deep
```
## Common “it broke” cases
### `moltbot: command not found`
### `openclaw: command not found`
Almost always a Node/npm PATH issue. Start here:
@@ -38,16 +38,16 @@ Almost always a Node/npm PATH issue. Start here:
Re-run the installer in verbose mode to see the full trace and npm output:
```bash
curl -fsSL https://molt.bot/install.sh | bash -s -- --verbose
curl -fsSL https://openclaw.bot/install.sh | bash -s -- --verbose
```
For beta installs:
```bash
curl -fsSL https://molt.bot/install.sh | bash -s -- --beta --verbose
curl -fsSL https://openclaw.bot/install.sh | bash -s -- --beta --verbose
```
You can also set `CLAWDBOT_VERBOSE=1` instead of the flag.
You can also set `OPENCLAW_VERBOSE=1` instead of the flag.
### Gateway “unauthorized”, can’t connect, or keeps reconnecting
@@ -59,10 +59,10 @@ You can also set `CLAWDBOT_VERBOSE=1` instead of the flag.
- [Gateway troubleshooting](/gateway/troubleshooting)
- [Control UI](/web/control-ui#insecure-http)
### `docs.molt.bot` shows an SSL error (Comcast/Xfinity)
### `docs.openclaw.ai` 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.
Some Comcast/Xfinity connections block `docs.openclaw.ai` via Xfinity Advanced Security.
Disable Advanced Security or add `docs.openclaw.ai` 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
@@ -82,7 +82,7 @@ Disable Advanced Security or add `docs.molt.bot` to the allowlist, then retry.
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`
- Check the allowlist: `openclaw 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
@@ -91,7 +91,7 @@ only those provider/model keys can be selected.
Paste a safe report:
```bash
moltbot status --all
openclaw status --all
```
If you can, include the relevant log tail from `moltbot logs --follow`.
If you can, include the relevant log tail from `openclaw logs --follow`.