Skip to main content

Connect Statsig to GitHub Copilot

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

Set up

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

    Add Statsig 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 Statsig’s 93 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Statsig

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

  4. 4

    Use Statsig from GitHub Copilot

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

Tools

93 Statsig tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call.

  • Approve autotune review

    Approve an in-flight review of an autotune experiment.

  • Approve dynamic config review

    Approve an in-flight review of a dynamic config.

  • Approve experiment review

    Approve an in-flight review of an experiment (A/B test).

  • Approve gate review

    Approve an in-flight review of a gate (feature flag).

  • Cancel autotune review

    Cancel (withdraw) an in-flight review of an autotune experiment.

  • Cancel dynamic config review

    Cancel (withdraw) an in-flight review of a dynamic config.

  • Cancel experiment review

    Cancel (withdraw) an in-flight review of an experiment (A/B test).

  • Cancel gate review

    Cancel (withdraw) an in-flight review of a gate (feature flag).

See all 93 Statsig 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 Statsig 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