Skip to main content
Book a demo

Connect Runlayer to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

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

    Add Runlayer 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 Runlayer’s 139 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 Runlayer

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

  4. 4

    Use Runlayer from GitHub Copilot CLI

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

Tools

139 Runlayer tools in GitHub Copilot CLI

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

  • Add agent connectors

    Add or update connectors on an agent (incremental edit).

  • Add agent skills

    Add skills to an agent (incremental edit).

  • Add agent subagent

    Add one subagent to an existing agent.

  • Add AI watch enforce entry

    Put one source in an Enforce allowlist or Protect denylist.

  • Add plugin connectors

    Add or update connectors on a plugin (incremental edit).

  • Add plugin skills

    Add skills to a plugin (incremental edit).

  • Create agent

    Create a new agent.

  • Create agent eval

    Create an offline eval run: replay selected past agent runs, optionally with overrides, and judge the replays.

See all 139 Runlayer 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 Runlayer 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