Summary

When Openclaw runs automated steps in the OpenClaw-managed isolated browser (Brave), the browser automation often stops mid-task. The agent reports it “can’t reach the openclaw browser control service (timed out after 15000ms)” even though the gateway is still running and openclaw gateway status shows RPC probe OK. In some cases, the CDP port (18800) ends up stuck “in use,” requiring manual cleanup.

Steps to reproduce

1. Start the isolated OpenClaw browser profile openclaw (Brave).
2. Open Keap login (https://keap.com/login or redirect via keap.com (http://keap.com/) “Log in”). but its any site really.
3. Perform a few automated actions (navigate, click buttons, fill fields).
4. After some actions, automation fails with the “browser control service timed out” error and stops.

Expected behavior

What did you expect to happen?• browser.start reliably launches and keeps the isolated Brave automation session controllable.
• Normal navigation/clicking shouldn’t cause the browser control channel to become unreachable.
• If the browser crashes/closes, OpenClaw should detect it and recover cleanly.
Actual behavior / errors

• During navigation or clicks: • Can't reach the openclaw browser control service (timed out after 15000ms). Start (or restart) the OpenClaw gateway...

• Sometimes after a failure: • PortInUseError: Port 18800 is already in use.
• Only resolved by finding/killing the stray process holding 18800.

Actual behavior

1. Start the isolated OpenClaw browser profile openclaw (Brave).
2. Open Keap login (https://keap.com/login or redirect via keap.com (http://keap.com/) “Log in”).
3. Perform a few automated actions (navigate, click buttons, fill fields).
4. After some actions, automation fails with the “browser control service timed out” error and stops.

Environment

• OS: Ubuntu 24.04 (noble)
• OpenClaw version: 2026.1.29 (gateway running as systemd user service)
• Browser: OpenClaw isolated browser profile openclaw (auto-detected Brave at /usr/bin/brave-browser)
• CDP port: 18800 (openclaw profile)
• Target website: its really any website we tried. but we used a logged in web app called keap.com. but stops on any site automation after a few loops.
• Channel: Telegram bot

##What we tried
• Restarting the gateway (SIGUSR1 / openclaw gateway restart) sometimes temporarily helps.
• Stopping/starting the browser profile.
• Killing stray browser processes when port 18800 is stuck.
Logs / artifacts

• openclaw-2026-02-06.log
• I can provide timestamps + excerpts around: • Browser control service ready
• subsequent browser failed: Can't reach... timed out
• any PortInUseError: 18800