Skip to main content
Book a demo

Connect AirOps to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

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

    GitHub Copilot setup guide
  3. 3

    Sign in to AirOps

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

  4. 4

    Use AirOps from GitHub Copilot

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

Tools

100 AirOps tools in GitHub Copilot

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

  • Accept opportunity

    Accept pending opportunities for a campaign and add them to the campaign action grid.

  • Add AEO region

    Add a region (ISO alpha-2 country code) to a Brand Kit's configured AEO regions.

  • Add grid column

    Add a new column to a grid table.

  • Analytics chart

    Query analytics data and display it as an interactive chart.

  • Automated feedback report

    AirOps only feedback tool.

  • Bulk update AEO prompt tags

    Apply a single tag operation (add or remove) to a batch of AEO prompts in one Brand Kit, atomically.

  • Bulk update AEO prompt topics

    Reassign a batch of AEO prompts to an existing topic in one Brand Kit.

  • Commit AEO prompt assignments

    Commit the current prompt-assignment draft for a Brand Kit to live.

See all 100 AirOps 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 AirOps 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