Skip to main content
Book a demo

Connect Glean to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Glean

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

  4. 4

    Use Glean from GitHub Copilot

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

Tools

16 Glean tools in GitHub Copilot

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

  • Brave actions web search

    Searches the web for up-to-date external information from the web.

  • Chat

    AI-powered tool for company knowledge.

  • Code search

    Searches company code and configuration (top matches only).

  • Create image

    Generate a new image from a natural-language prompt using Glean's image generation models, save it as an IMAGE artifact in the user's Library, and return links to view or download it.

  • Edit image

    Modify an existing IMAGE artifact using a natural-language instruction.

  • Employee search

    Finds company employees and their information.

  • Gmail search

    Searches Gmail inbox (Google Workspace) for emails, conversations, and attachments.

  • Meeting lookup

    Searches company calendar meetings and extracts transcripts.

See all 16 Glean 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 Glean 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