Skip to main content
Book a demo

Connect Playwright to VS Code

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

Book a demo VS Code setup guide

Set up

Add Playwright to VS Code in four steps

Admins approve the server once. Everyone in VS Code 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 VS Code to Runlayer

    Install the Runlayer CLI so VS Code can reach Playwright, which runs on the user’s machine. Auto Sync can then write Playwright into VS Code on macOS, Windows, and Linux.

    VS Code 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 VS Code

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

Tools

27 Playwright tools in VS Code

Runlayer policy decides which of these VS Code 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 VS Code

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, VS Code 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 VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination