Browser Control Service Timing Out
In short, when I'm on Grok Imagine or X and I'm trying to click or reply to a post or trying to get it to submit prompts I'm having issues as stated below, this must be for all sites that require some input so not sure why more people arent experiencing the issue, I'm not seeing it flagged anyway yet...
Chrome extension relay connects to OpenClaw (port 18792) so I Openclaw control your existing Chrome tabs,
When I try to click/type, there's a timeout — the command never reaches the page properly,
This breaks X automation completely (can't like, reply, follow, etc.)
Environment
OS: macOS (Mac Mini)
Primary Model is Minimax M2.5
OpenClaw Version: 2026.2.26
But have been battling the issue in .24 and .25 (25 Was working yesterday it could reply and generate images)
Anyone else having any issues with Browser Timeouts?
The Current Issue (v2026.2.26)
The Relay connection is healthy (Port 18792 is green, token is accepted). I can Maps to pages and use press key for single keystrokes successfully. However, any action requiring an element reference (ref) is completely broken.
Symptoms: click, fill, and hover commands result in a consistent 20,000ms timeout.
Behavior: The agent can see the page (snapshots work), but it cannot "touch" it. It feels like the command bridge for element-specific actions is failing to execute or is being dropped by the control service.
Version History & Regression Path
v2026.2.24: This version was unusable for me due to the Browser Control Service timeout.
v2026.2.25: This version was working perfectly yesterday. I was able to run automated reports on X.com without issue. Clicks and fills were responsive. It only began failing late in the day for no apparent reason (potential session/CDP hang).
v2026.2.26 (Latest): Updated today, and while the relay connection logic feels more stable, the element interaction regression is back. I am once again getting the 20s timeouts on all act commands despite a "Green" status.
Chrome extension relay connects to OpenClaw (port 18792) so I Openclaw control your existing Chrome tabs,
When I try to click/type, there's a timeout — the command never reaches the page properly,
This breaks X automation completely (can't like, reply, follow, etc.)
Environment
OS: macOS (Mac Mini)
Primary Model is Minimax M2.5
OpenClaw Version: 2026.2.26
But have been battling the issue in .24 and .25 (25 Was working yesterday it could reply and generate images)
Anyone else having any issues with Browser Timeouts?
The Current Issue (v2026.2.26)
The Relay connection is healthy (Port 18792 is green, token is accepted). I can Maps to pages and use press key for single keystrokes successfully. However, any action requiring an element reference (ref) is completely broken.
Symptoms: click, fill, and hover commands result in a consistent 20,000ms timeout.
Behavior: The agent can see the page (snapshots work), but it cannot "touch" it. It feels like the command bridge for element-specific actions is failing to execute or is being dropped by the control service.
Version History & Regression Path
v2026.2.24: This version was unusable for me due to the Browser Control Service timeout.
v2026.2.25: This version was working perfectly yesterday. I was able to run automated reports on X.com without issue. Clicks and fills were responsive. It only began failing late in the day for no apparent reason (potential session/CDP hang).
v2026.2.26 (Latest): Updated today, and while the relay connection logic feels more stable, the element interaction regression is back. I am once again getting the 20s timeouts on all act commands despite a "Green" status.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
