Skip to main content
Book a demo

Connect Chrome DevTools to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add Chrome DevTools 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 Chrome DevTools in Runlayer

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

  2. 2

    Connect GitHub Copilot to Runlayer

    Install the Runlayer CLI so GitHub Copilot can reach Chrome DevTools, which runs on the user’s machine.

    GitHub Copilot setup guide
  3. 3

    Sign in to Chrome DevTools

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

  4. 4

    Use Chrome DevTools from GitHub Copilot

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

Tools

26 Chrome DevTools tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call. 10 read data only.

  • Click

    Clicks on the provided element

  • Close page

    Closes the page by its index.

  • Drag

    Drag an element onto another element

  • Emulate

    Emulates various features on the selected page.

  • Evaluate script

    Evaluate a JavaScript function inside the currently selected page.

  • Fill

    Type text into a input, text area or select an option from a element.

  • Fill form

    Fill out multiple form elements at once

  • Get console message

    Gets a console message by its ID.

See all 26 Chrome DevTools 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 Chrome DevTools 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