Skip to main content
Book a demo

Connect Grain to GitHub Copilot CLI

Give GitHub Copilot CLI governed access to Grain’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 Grain 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 Grain in Runlayer

    Add Grain 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 Grain’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 Grain

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

  4. 4

    Use Grain from GitHub Copilot CLI

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

Tools

15 Grain tools in GitHub Copilot CLI

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

  • Myself

    Get information about the logged-in Grain user.

  • List meetings

    Returns a filtered list of Grain meetings you have access to, ordered by most recent.

  • List attended meetings

    Returns a filtered list of Grain meetings you have attended, ordered by most recent.

  • Fetch meeting

    Fetches information about a single Grain meeting by ID.

  • Fetch meeting notes

    Fetches the AI notes payload from a single Grain meeting by ID.

  • Fetch meeting transcript

    Fetches the transcript from a single Grain meeting by ID.

  • Search persons

    Returns a filtered list of persons that were participants of Grain meetings you have access to.

  • Search companies

    Returns a filtered list of companies that were participants of Grain meetings you have access to.

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