Fix Browser Gateway Timeout (15000ms)
Connection Interrupted
The 15000ms timeout indicates that the Gateway is trying to talk to your Browser, but the communication channel is blocked or unauthorized.
Seeing [tools] browser failed: gateway timeout after 15000ms? This usually happens when the extension relay loses its heartbeat connection to the local gateway.
Next Step
Fix now, then reduce repeat incidents
If this issue keeps coming back, validate your setup in Doctor first, then harden your config.
1. Check Extension Auth Token
The most common cause is a token mismatch. If you recently updated OpenClaw or rotated your tokens, the browser extension might still be using an old one.
- Open Chrome/Edge and click the OpenClaw Extension icon.
- Ensure the Gateway Auth Token field matches your
openclaw.json. - Click Save and refresh your active tabs.
2. Verify Gateway Port (18789)
The extension relay connects via WebSockets to port 18789 by default. If this port is blocked by a firewall or another service, it will time out.
# macOS/Linux\nlsof -i :18789\n\n# Windows (PowerShell)\nnetstat -ano | findstr :18789
3. Increase Local LLM Timeout
Sometimes the "browser timeout" is actually caused by the LLM taking too long to generate the navigation command. If your machine is under heavy load, increase the global timeout.
Update openclaw.json
"agents": {
"defaults": {
"timeoutSeconds": 60 // Increase from 30
}
}4. Fast Recovery Command
If everything looks correct but the timeout persists, use this sequence to force a fresh handshake:
openclaw gateway stop\n# Close all browser tabs\nopenclaw gateway start\n# Open browser and wait for extension 'Connected' status
Pro Tip: Headless Mode
If you are running on a server without a UI, make sure you are using a CDP Provider (like Browserless) instead of the Extension Relay. See our Automation Guide.
Did this guide solve your problem?