Skip to main content
Book a demo

Connect Jam to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

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

    Add Jam 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 Jam’s 15 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 Jam

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

  4. 4

    Use Jam from GitHub Copilot CLI

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

Tools

15 Jam tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI users can call. 13 read data only.

  • Get Jam bug report details and metadata

    Retrieve comprehensive metadata and details for a specific Jam bug report.

  • Get network activity and HTTP request logs

    Extract network activity logs captured during the Jam session.

  • Get browser console output and javascript logs

    Retrieve browser console output captured during the Jam session.

  • Get user interaction timeline and events

    Access the complete timeline of user interactions captured in the Jam.

  • Get custom Jam metadata

    Retrieve custom metadata set via the jam.metadata() SDK.

  • Get visual screenshots and image attachments

    Retrieve visual screenshots and image attachments from screenshot-type Jams.

  • Analyze video recording

    Extract user intents from a Jam recording.

  • Get video transcript

    Retrieve the speech transcript (captions) from a video Jam recording in WebVTT format with timestamps.

See all 15 Jam 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 Jam 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