Headless Chromium browser sandbox that can be controlled via Chrome DevTools Protocol (CDP). Use this with OpenClaw or other services that need browser automation capabilities.
Zeabur
Zeabur
ZeaburA headless Chromium browser that can be controlled via Chrome DevTools Protocol (CDP).
Other services in the same Zeabur project can connect via:
http://openclaw-sandbox-browser:9222
GET /json/version - Browser version infoGET /json/list - List open tabsGET /json/new?url=<url> - Open new tabOption 1: Paste config to OpenClaw Copy the following configuration and paste it to OpenClaw chat, asking it to update your config file:
"browser": {
"enabled": true,
"attachOnly": true,
"defaultProfile": "remote",
"profiles": {
"remote": {
"cdpUrl": "http://openclaw-sandbox-browser:9222",
"color": "#FF4500"
}
}
}
Example prompt: "Please add this browser configuration to my openclaw.json file"
Option 2: OpenClaw Web UI
remoteremotehttp://openclaw-sandbox-browser:9222#FF4500 (optional)For detailed configuration options, see the official documentation.
After deploying, test the connection using curl from OpenClaw terminal:
curl http://openclaw-sandbox-browser:9222/json/version
If successful, you should see a JSON response like:
{"Browser":"Chrome/...","Protocol-Version":"1.3",...}
The following error messages in logs are normal and can be safely ignored:
Failed to connect to the bus - No D-Bus in container (expected)Failed to adjust OOM score - Permission limitation (doesn't affect functionality)DEPRECATED_ENDPOINT - Google Cloud Messaging not needed for headless mode