Skip to main content
Book a demo

Connect GitHub to Claude Code

Give Claude Code governed access to GitHub’s 100 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude Code setup guide

Set up

Add GitHub to Claude Code in four steps

Admins approve the server once. Everyone in Claude Code then gets it through the same governed connection.

  1. 1

    Approve GitHub in Runlayer

    Add GitHub from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, GitHub’s 100 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code setup guide
  3. 3

    Sign in to GitHub

    Each user signs in to GitHub with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use GitHub from Claude Code

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

Tools

100 GitHub tools in Claude Code

Runlayer policy decides which of these Claude Code users can call.

  • Get actions

    Get details about specific GitHub Actions resources.

  • List actions

    Tools for listing GitHub Actions resources.

  • Actions run trigger

    Trigger GitHub Actions workflow operations, including running, re-running, cancelling workflow runs, and deleting workflow run logs.

  • Add comment to pending review

    Add review comment to the requester's latest pending pull request review.

  • Add issue comment

    Add a comment and/or reaction to a specific issue or issue comment in a GitHub repository.

  • Add reply to pull request comment

    Add a reply and/or reaction to an existing pull request comment.

  • Assign copilot to issue

    Assign Copilot to a specific issue in a GitHub repository.

  • Assign copilot to issue with intent

    Assign Copilot to a specific issue in a GitHub repository.

See all 100 GitHub tools

Control

What Runlayer can see and stop in Claude Code

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

  • Gateway policy (available)

    Every GitHub call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude Code 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.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • OTLP telemetry (available)

    Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Claude Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Claude Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.

In Claude Code

  • When a tool fails, Runlayer records the error but cannot hide it.

Frequently asked questions

Connect more

Find another combination