Skip to main content
Book a demo

Connect Honeycomb to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

Add Honeycomb 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

    Add Honeycomb to Runlayer

    Honeycomb isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  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 Honeycomb’s 38 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 Honeycomb

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

  4. 4

    Use Honeycomb from GitHub Copilot CLI

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

Tools

38 Honeycomb tools in GitHub Copilot CLI

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

  • Canvas agent invoke

    Kick off a single-turn run of the Honeycomb Canvas agent.

  • Canvas agent poll response

    Poll for the result of a previously-issued canvas_agent_invoke call.

  • Create board

    Create a board (dashboard) with query, SLO, and text panels.

  • Create burn alert

    Create a burn alert on an SLO.

  • Create marker

    Creates a marker (a vertical annotation on charts) to mark a point or window in time, such as a deploy, incident, or config change.

  • Create recipient

    Create a notification recipient (email, Slack, PagerDuty, or webhook) so it can be attached to triggers, SLO burn alerts, and Anomaly Detection.

  • Create slo

    Create an SLO (Service Level Objective) backed by an auto-created SLI derived column.

  • Create trigger

    Create a trigger that fires alerts when a query result crosses a threshold.

See all 38 Honeycomb 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 Honeycomb 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