Connect Playwright to Warp
Give Warp governed access to Playwright’s 27 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Playwright to Warp in four steps
Admins approve the server once. Everyone in Warp then gets it through the same governed connection.
- 1
Approve Playwright in Runlayer
Add Playwright from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Warp to Runlayer
Install the Runlayer CLI so Warp can reach Playwright, which runs on the user’s machine.
Warp setup guide - 3
Sign in to Playwright
Sign in the way Playwright requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Playwright from Warp
Playwright’s approved tools appear in Warp. Every call is checked against policy and recorded.
Tools
27 Playwright tools in Warp
Runlayer policy decides which of these Warp users can call.
Browser click
Perform click on a web page
Browser close
Close the page
Browser console messages
Returns all console messages
Browser drag
Perform drag and drop between two elements
Browser drop
Drop files or MIME-typed data onto an element, as if dragged from outside the page.
Browser emulate media
Emulate CSS media features for the page, for example switch between the light and dark color scheme.
Browser evaluate
Evaluate JavaScript expression on page or element
Browser file upload
Upload one or multiple files
Control
What Runlayer can see and stop in Warp
Some controls apply to every client at the gateway. Others depend on what Warp exposes to Runlayer.
Gateway policy (available)
Every Playwright call from Warp passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Warp as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Warp yet, so control happens at the gateway.
Frequently asked questions
Connect more