Skip to main content

Connect Grain to GitHub Copilot

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

Set up

Add Grain to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot 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 to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Grain’s 15 tools through the plugin’s search and execute tools.

    GitHub Copilot 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

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

Tools

15 Grain tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot 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

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.

  • Gateway policy (available)

    Every Grain call from GitHub Copilot 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 as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination