Browser tool | Friends of the Crustacean 🦞🤝 | Page 1

woeful minnow Apr 23, 2026, 10:42 AM

#

Do open claw need to install playwright or does it already have a builtin browser tool and how to use it

pine jackalBOT Apr 23, 2026, 10:42 AM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

white coyoteBOT Apr 23, 2026, 10:42 AM

#

tame fogBOT Apr 23, 2026, 10:43 AM

#

Nope, you normally do not need to install Playwright separately.

OpenClaw already has a built-in browser tool. It ships as the bundled browser plugin and uses Playwright internally.

Quick start:

openclaw browser status
openclaw browser start
openclaw browser open https://example.com
openclaw browser snapshot

A few useful notes:

Default profile is openclaw, an isolated agent-controlled browser.
There is also a user profile if you want it to attach to your real signed-in Chrome/Brave session.

#

Make sure this is enabled in ~/.openclaw/openclaw.json:

{
  browser: {
    enabled: true
  }
}

If openclaw browser is missing, the usual cause is plugins.allow excluding browser.

Docs:

If you want, I can also give you a minimal config example for local use or explain how to use it from an agent prompt.

woeful minnow Apr 23, 2026, 10:46 AM

#

Yeah — I read it.

That text doesn’t match this machine’s current install.

What I verified here:

• openclaw --help shows no browser top-level CLI command
• this install is OpenClaw 2026.4.21
• the agent browser tool does exist and works partly:
• open
• snapshot
• status
• but interactive actions still fail/timeo out:
• act:click
• profiles

So my read is:

Your pasted note is likely from different docs / a different OpenClaw version
• maybe newer docs
• maybe another install/build
On this Mac, there is not a working openclaw browser ... CLI surface I can use directly
The built-in browser capability is present, but the interactive browser bridge is unhealthy

So you weren’t wrong to question it — I’m glad you pasted that.

If you want, next I can do one precise check:

• whether this install is missing a CLI/browser plugin registration
• or whether it’s just the host browser session stuck

My guess: stuck host/browser bridge, not missing config.

My agent answer

tame fogBOT Apr 23, 2026, 10:47 AM

#

Yeah, you were right to push back. I overgeneralized from the current docs.

The safer version is:

You do not need to install Playwright separately for normal OpenClaw browser use.
The browser capability is built in.
But on some 2026.4.x installs, the agent/browser tool can exist even when openclaw browser ... is not exposed the way the live docs show.

Given that open, snapshot, and status work for you, this does not look like “Playwright is missing”.
It looks more like one of these:

CLI/plugin registration mismatch
stuck user / existing-session browser bridge
browser profile/runtime issue, especially for interactive actions like click

The next precise checks I’d use are:

#

openclaw plugins list
openclaw plugins doctor
openclaw config get browser
openclaw config get plugins
openclaw logs --follow

Two especially useful questions:

Do clicks fail on the default isolated openclaw profile too, or only on user / your real browser?
Does plugins list show the browser plugin loaded?

If it only fails on user, I’d suspect the host browser attach path.
If it fails on openclaw too, I’d suspect the browser runtime/plugin side.

Docs I was referring to, but they may be ahead of your effective install surface:

#

If you paste the output of those 4 commands, I can narrow it down pretty fast.

woeful minnow Apr 23, 2026, 10:51 AM

#

my agent: Good — this narrows it down.

What I checked:

• openclaw config get browser → browser is enabled, default profile is clawd
• openclaw config get plugins → browser plugin is enabled
• earlier browser status also showed:
• driver: openclaw
• transport: cdp
• running: true
• profile: clawd

So the key point is:

• this is failing on the default isolated profile (clawd)
• not just on a user / attached real browser session

That strongly suggests:

• not a user-browser attach issue
• not “browser plugin disabled”
• more likely a browser runtime / plugin-side problem in this install

Also interesting:

• openclaw plugins list and openclaw plugins doctor both seemed to hang, which makes me a bit suspicious of the plugin/runtime state too.

My current best diagnosis:

browser plugin is present and enabled
isolated browser profile exists
read-only browser actions work
interactive browser actions are broken at the runtime/plugin layer

So yes — your pushback was right. This is not simply “Playwright missing” anymore.

Best next move now:

• clean reinstall/update OpenClaw with browser support, rather than more patching in place

If you want, I can help you do that step-by-step next.

tame fogBOT Apr 23, 2026, 10:53 AM

#

That diagnosis looks basically right, except I would not jump straight to a clean reinstall.

What I’d say instead:

clawd is a legacy browser/profile name, not the bug by itself.
Since the isolated profile is running and can do open / snapshot / status, this is not “Playwright missing”.
This really does look more like a browser runtime / plugin regression on that install.
Also, yes, the live docs can be ahead of what a specific release exposes.

My recommendation order would be:

Update first, don’t clean-reinstall first
```
openclaw update
```
If it was installed via package manager, follow the normal update flow here: https://docs.openclaw.ai/install/updating

#

Restart the gateway
Reproduce one failing click while tailing logs
```
openclaw logs --follow
```
If it still breaks, treat it as a bug and file an issue with:
- openclaw --version
- the failing browser action
- the relevant log snippet
  https://github.com/openclaw/openclaw/issues

So the short version is:

No separate Playwright install needed
Built-in browser is present

#

Your current problem looks like a runtime bug/regression, not missing setup

Relevant docs:

If you want, I can help you turn that into a tight “next 3 commands” reply for the thread.

woeful minnow Apr 23, 2026, 11:04 AM

#

11:00:15+00:00 error [tools] browser failed: timed out. Restart the OpenClaw gateway (OpenClaw.app menubar, or openclaw gateway). Do NOT retry the browser tool — it will keep failing. Use an alternative approach or inform the user that the browser is currently unavailable. raw_params={"action":"act","target":"host","targetId":"F2885138E9E9E5268F4A5DF8B0AE793F","request":{"kind":"click","ref":"ax44","timeoutMs":20000}}

11:00:26+00:00 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ sessions.list 153ms conn=4d486f7e…e475 id=0b9a17ef…affa

11:00:27+00:00 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ sessions.list 63ms conn=95457ede…f99a id=873b992f…7bcd

11:00:27+00:00 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ chat.history 151ms conn=95457ede…f99a id=e851ba21…bdf0

this is the log

#

Best snippet to send Krill is just this:

11:00:15+00:00 error [tools] browser failed: timed out. Restart the OpenClaw gateway (OpenClaw.app menubar, or openclaw gateway). Do NOT retry the browser tool — it will keep failing. Use an alternative approach or inform the user that the browser is currently unavailable. raw_params={"action":"act","target":"host","request":{"kind":"click","ref":"ax44","timeoutMs":20000}}

And add:

• openclaw --version → 2026.4.21
• browser plugin loaded
• open/snapshot/status work
• act:click fails on isolated profile clawd

tame fogBOT Apr 23, 2026, 11:04 AM

#

Yep, that’s the smoking gun.

That log confirms:

the browser tool is present
this is not a missing-Playwright problem
the current browser runtime/session is wedged
retrying the browser tool without a restart is pointless, the tool is explicitly saying that

Best next step:

openclaw gateway restart
openclaw status

Then try one simple browser action again. Not a bunch of retries.

#

If the first click after restart fails the same way, I’d move to:

openclaw update

And if it still happens after update, that’s GitHub-issue territory, with that exact log attached:
https://github.com/openclaw/openclaw/issues

So the short answer for the thread is:

OpenClaw already has a built-in browser tool, no separate Playwright install needed.
Your logs show the browser runtime timed out and needs a gateway restart. If it keeps happening after restart, update OpenClaw, then file an issue if it still reproduces.

Docs:

#

If you want, I can help you turn that into a clean final reply to post.

woeful minnow Apr 23, 2026, 11:05 AM

#

Best snippet to send Krill is just this:

11:00:15+00:00 error [tools] browser failed: timed out. Restart the OpenClaw gateway (OpenClaw.app menubar, or openclaw gateway). Do NOT retry the browser tool — it will keep failing. Use an alternative approach or inform the user that the browser is currently unavailable. raw_params={"action":"act","target":"host","request":{"kind":"click","ref":"ax44","timeoutMs":20000}}

And add:

• openclaw --version → 2026.4.21
• browser plugin loaded
• open/snapshot/status work
• act:click fails on isolated profile clawd

tame fogBOT Apr 23, 2026, 11:07 AM

#

Yep, that’s the right summary.

I’d send it like this, just a bit tighter:

Relevant log:

11:00:15+00:00 error [tools] browser failed: timed out. Restart the OpenClaw gateway (OpenClaw.app menubar, or `openclaw gateway restart`). Do NOT retry the browser tool, it will keep failing. Use an alternative approach or inform the user that the browser is currently unavailable.
raw_params={"action":"act","target":"host","request":{"kind":"click","ref":"ax44","timeoutMs":20000}}

Context:
- openclaw --version: 2026.4.21
- browser plugin is loaded
- open / snapshot / status work
- act:click fails on the isolated `clawd` profile

#

Conclusion:
This is not “Playwright missing”.
The built-in browser exists, but the browser runtime timed out and needs a gateway restart.
If it still reproduces after restart, update OpenClaw. If it still fails after that, file a GitHub issue.

That gets the important bits across cleanly.

woeful minnow Apr 23, 2026, 11:07 AM

#

so what do I do now?

tame fogBOT Apr 23, 2026, 11:08 AM

#

Yep, that’s the right snippet.

Only tweak I’d make is this command:

use openclaw gateway restart
not just openclaw gateway

Everything else in your summary looks solid.

#

Right now, do this:

Restart the gateway
```
openclaw gateway restart
```
Try one simple browser action again once
- for example open or a single click
- don’t spam retries
If the first try after restart fails the same way, update OpenClaw
```
openclaw update
openclaw gateway restart
```

#

If it still fails after update, file a bug with:
- openclaw --version
- the log snippet you pasted
- note that open/snapshot/status work but act:click fails on clawd

GitHub issues: https://github.com/openclaw/openclaw/issues

So, short version: no, you do not need to install Playwright, your built-in browser tool is there, it just got stuck and needs a restart, or possibly an update.

woeful minnow Apr 23, 2026, 11:11 AM

#

what could be the issues? may be the browser is too old?

tame fogBOT Apr 23, 2026, 11:12 AM

#

Maybe, but not my first guess.

Important detail: the 144+ browser version check in the docs is for profile="user" / existing-session attach, not the isolated clawd / openclaw managed profile you’re failing on.

Given your logs, the more likely causes are:

wedged browser runtime/session
the timeout message literally says restart the gateway and don’t retry
browser plugin/runtime bug or regression
especially since open/snapshot/status work but act:click wedges
stale gateway state after a bad browser action
one timed-out interaction can poison the browser session until restart
possibly an old or weird local Chromium binary, but this is a weaker guess here

#

So I’d rank it like this:

most likely: runtime/session bug
less likely: browser too old

If you want to rule out browser age anyway, update your local Chrome/Brave/Edge/Chromium and restart the gateway. But I’d do this order first:

openclaw gateway restart
openclaw update
openclaw gateway restart

If it still reproduces after that, I’d treat it as a bug and file it:
https://github.com/openclaw/openclaw/issues

Docs:

#

woeful minnow Apr 24, 2026, 6:10 AM

#

given other topic it seem like there is current an issue with browser tool of openclaw right? can you check accross the git issues or ask topic in this discord help

tame fogBOT Apr 24, 2026, 6:12 AM

#

Yeah, I checked, and this does look like a real current rough spot, not just you.

I checked existing GitHub issues and recent Discord help/forum threads. There are multiple matching reports:

GitHub examples

#11518 persistent timeout on browser.act with profile="openclaw"
#14503 open / snapshot work, then act times out or says tab not found
#31586 browser tool times out while CLI/browser service still works
#24494 browser control service / macOS listening issues
#16589 generic “can’t reach the browser control service” failures

Discord help/forum examples

Error browser instance
Issue using Browser
CDP browser not working. again.

Those threads show similar symptoms:

#

CDP websocket ... not reachable after start
open / snapshot work but interactive actions fail
browser attach/detection weirdness on managed openclaw / clawd profiles

So my honest read is:

yes, there is/was an active cluster of browser-tool issues
especially around browser.act / click, managed browser profiles, and CDP/control-session state
it does not look like “you forgot to install Playwright”

I did not post in #help on your behalf, but I did search existing help threads.
If you want, the best next move is to make a focused #help forum post with:

openclaw --version
OS
exact log line
whether open / snapshot / status work

#

whether act:click fails on isolated clawd / openclaw

If you want, I can draft that post for you in one clean message.

woeful minnow Apr 24, 2026, 6:52 AM

#

so has it been an open issues on git for them to fix

tame fogBOT Apr 24, 2026, 6:53 AM

#

Yes, there have definitely been GitHub issues filed for browser-tool failures.

But the interesting part is: the matching ones I checked are already closed, for example:

So my read is:

this is not an unknown problem
fixes have apparently landed for earlier variants
but there may be recurring/regressing browser bugs, because recent Discord threads still show similar symptoms

#Browser tool