openclaw - 💡(How to fix) Fix Isolated session gateway missing full Playwright support [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#70493Fetched 2026-04-24 05:57:20
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

Error Message

error: Playwright is not available in this gateway build; 'navigate' is unsupported.

RAW_BUFFERClick to expand / collapse

Problem

When using the browser tool in an isolated sub-agent session, Playwright operations fail with:

error: Playwright is not available in this gateway build; 'navigate' is unsupported. Install the full Playwright package (not playwright-core) and restart the gateway.

Main session works fine with profile=user + Chrome remote debugging.

Environment

  • macOS
  • OpenClaw 2026.4.21 (f788c88)
  • Node.js 25.8.2
  • Isolated session gateway (all sub-agents)

Expected

Browser automation (navigate/snapshot/act) should work in isolated sessions just as in main session.

Actual

  • browser action=navigate: Playwright not available
  • browser action=snapshot: tab not found
  • browser action=act: selector targeting not supported in isolated session

Request

Ensure isolated session gateway includes full Playwright support so browser tool works consistently across all sessions.

extent analysis

TL;DR

Install the full Playwright package in the isolated session gateway to enable browser automation.

Guidance

  • The error message suggests that the playwright-core package is installed, but the full Playwright package is required for browser automation in isolated sessions.
  • Verify that the full Playwright package is installed by checking the package.json file or running npm ls playwright in the gateway directory.
  • To mitigate the issue, install the full Playwright package using npm install playwright or yarn add playwright in the gateway directory.
  • After installation, restart the gateway to ensure the changes take effect.

Notes

The issue seems to be specific to the isolated session gateway, and the main session works fine with the playwright-core package. The full Playwright package may have additional dependencies or requirements that need to be met.

Recommendation

Apply workaround: Install the full Playwright package in the isolated session gateway, as it is required for browser automation to work consistently across all sessions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Isolated session gateway missing full Playwright support [1 participants]