Skip to main content
Book a demo

Connect Playwright to Cline CLI

Give Cline CLI governed access to Playwright’s 27 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cline CLI setup guide

Set up

Add Playwright to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.

  1. 1

    Approve Playwright in Runlayer

    Add Playwright from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Cline CLI to Runlayer

    Install the Runlayer CLI so Cline CLI can reach Playwright, which runs on the user’s machine.

    Cline CLI setup guide
  3. 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. 4

    Use Playwright from Cline CLI

    Playwright’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.

Tools

27 Playwright tools in Cline CLI

Runlayer policy decides which of these Cline CLI 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

See all 27 Playwright tools

Control

What Runlayer can see and stop in Cline CLI

Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Playwright call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination