Skip to main content
Book a demo

Connect Buildkite to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

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

    Add Buildkite 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 Buildkite’s 71 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 Buildkite

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

  4. 4

    Use Buildkite from GitHub Copilot CLI

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

Tools

71 Buildkite tools in GitHub Copilot CLI

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

  • Access token

    Get information about the current API access token including its scopes and UUID

  • Cancel build

    Cancel a running build on a Buildkite pipeline

  • Compare builds

    Compare step outcomes, final-attempt retry counts and execution/scheduling times between builds in one pipeline.

  • Create annotation

    Create an annotation on a build or specific job.

  • Create build

    Trigger a new build on a Buildkite pipeline for a specific commit and branch, with optional environment variables, metadata, and author information

  • Create cache registry

    Create a cache registry in a cluster.

  • Create cluster

    Create a new cluster in an organization

  • Create cluster queue

    Create a new queue in a cluster

See all 71 Buildkite 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 Buildkite 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