Skip to main content
Book a demo

Connect Skyvern to VS Code

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

Book a demo VS Code setup guide

Set up

Add Skyvern 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 Skyvern in Runlayer

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

  2. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Skyvern’s 77 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 3

    Sign in to Skyvern

    Sign in the way Skyvern requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Skyvern from VS Code

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

Tools

77 Skyvern tools in VS Code

Runlayer policy decides which of these VS Code users can call. 34 read data only and 11 can change or delete data.

  • Create browser session

    Create a new browser session to start interacting with websites.

  • Close browser session

    Close a browser session when you're done.

  • List browser sessions

    List all active browser sessions.

  • Get browser session

    Get details about a specific browser session -- status, timeout, availability.

  • Connect to browser session

    Connect to an existing browser -- a cloud session by ID or any browser via CDP URL.

  • Perform browser action (ai)

    Perform actions on a page by describing what to do in plain English.

  • Extract data from page (ai)

    Extract structured data from the current page using AI with screenshots and a dedicated extraction LLM.

  • Validate page condition (ai)

    Check if a condition is true on the current page — cheapest AI option for yes/no questions.

See all 77 Skyvern 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 Skyvern 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