github/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-04-19 02:47:27 +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

32
docs/tools/browser-linux-troubleshooting.md
View File

@@ -1,5 +1,5 @@
---
summary: "Fix Chrome/Brave/Edge/Chromium CDP startup issues for Moltbot browser control on Linux"
summary: "Fix Chrome/Brave/Edge/Chromium CDP startup issues for OpenClaw browser control on Linux"
read_when: "Browser control fails on Linux, especially with snap Chromium"
---
@@ -7,14 +7,14 @@ read_when: "Browser control fails on Linux, especially with snap Chromium"
## Problem: "Failed to start Chrome CDP on port 18800"
Moltbot's browser control server fails to launch Chrome/Brave/Edge/Chromium with the error:
OpenClaw's browser control server fails to launch Chrome/Brave/Edge/Chromium with the error:
```
{"error":"Error: Failed to start Chrome CDP on port 18800 for profile \"clawd\"."}
{"error":"Error: Failed to start Chrome CDP on port 18800 for profile \"openclaw\"."}
```
### Root Cause
On Ubuntu (and many Linux distros), the default Chromium installation is a **snap package**. Snap's AppArmor confinement interferes with how Moltbot spawns and monitors the browser process.
On Ubuntu (and many Linux distros), the default Chromium installation is a **snap package**. Snap's AppArmor confinement interferes with how OpenClaw spawns and monitors the browser process.
The `apt install chromium` command installs a stub package that redirects to snap:
```
@@ -34,7 +34,7 @@ sudo dpkg -i google-chrome-stable_current_amd64.deb
sudo apt --fix-broken install -y # if there are dependency errors
```
Then update your Moltbot config (`~/.clawdbot/moltbot.json`):
Then update your OpenClaw config (`~/.openclaw/openclaw.json`):
```json
{
@@ -49,7 +49,7 @@ Then update your Moltbot config (`~/.clawdbot/moltbot.json`):
### Solution 2: Use Snap Chromium with Attach-Only Mode
If you must use snap Chromium, configure Moltbot to attach to a manually-started browser:
If you must use snap Chromium, configure OpenClaw to attach to a manually-started browser:
1. Update config:
```json
@@ -67,19 +67,19 @@ If you must use snap Chromium, configure Moltbot to attach to a manually-started
```bash
chromium-browser --headless --no-sandbox --disable-gpu \
--remote-debugging-port=18800 \
--user-data-dir=$HOME/.clawdbot/browser/clawd/user-data \
--user-data-dir=$HOME/.openclaw/browser/openclaw/user-data \
about:blank &
```
3. Optionally create a systemd user service to auto-start Chrome:
```ini
# ~/.config/systemd/user/clawd-browser.service
# ~/.config/systemd/user/openclaw-browser.service
[Unit]
Description=Clawd Browser (Chrome CDP)
Description=OpenClaw Browser (Chrome CDP)
After=network.target
[Service]
ExecStart=/snap/bin/chromium --headless --no-sandbox --disable-gpu --remote-debugging-port=18800 --user-data-dir=%h/.clawdbot/browser/clawd/user-data about:blank
ExecStart=/snap/bin/chromium --headless --no-sandbox --disable-gpu --remote-debugging-port=18800 --user-data-dir=%h/.openclaw/browser/openclaw/user-data about:blank
Restart=on-failure
RestartSec=5
@@ -87,7 +87,7 @@ RestartSec=5
WantedBy=default.target
```
Enable with: `systemctl --user enable --now clawd-browser.service`
Enable with: `systemctl --user enable --now openclaw-browser.service`
### Verifying the Browser Works
@@ -115,15 +115,15 @@ curl -s http://127.0.0.1:18791/tabs
### Problem: "Chrome extension relay is running, but no tab is connected"
You’re using the `chrome` profile (extension relay). It expects the Moltbot
You’re using the `chrome` profile (extension relay). It expects the OpenClaw
browser extension to be attached to a live tab.
Fix options:
1. **Use the managed browser:** `moltbot browser start --browser-profile clawd`
(or set `browser.defaultProfile: "clawd"`).
1. **Use the managed browser:** `openclaw browser start --browser-profile openclaw`
(or set `browser.defaultProfile: "openclaw"`).
2. **Use the extension relay:** install the extension, open a tab, and click the
Moltbot extension icon to attach it.
OpenClaw extension icon to attach it.
Notes:
- The `chrome` profile uses your **system default Chromium browser** when possible.
- Local `clawd` profiles auto-assign `cdpPort`/`cdpUrl`; only set those for remote CDP.
- Local `openclaw` profiles auto-assign `cdpPort`/`cdpUrl`; only set those for remote CDP.