Skip to main content
Book a demo

Connect Skyvern to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add Skyvern to GitHub Copilot in four steps

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

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Skyvern’s 77 tools through the plugin’s search and execute tools.

    GitHub Copilot 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 GitHub Copilot

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

Tools

77 Skyvern tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot 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 GitHub Copilot

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

  • Gateway policy (available)

    Every Skyvern call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination