Skip to main content
Book a demo

Connect Glean to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

Add Glean to GitHub Copilot CLI in four steps

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

    Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Glean’s 16 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

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

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

Tools

16 Glean tools in GitHub Copilot CLI

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

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

  • Gateway policy (available)

    Every Glean call from GitHub Copilot CLI 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 CLI as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call or permission request before GitHub Copilot CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.

In GitHub Copilot CLI

  • When a tool fails, Runlayer records the error but cannot replace it.

Frequently asked questions

Connect more

Find another combination