Skip to main content
Book a demo

Connect GitHub to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add GitHub to Cline CLI in four steps

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

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches GitHub’s 100 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI 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 Cline CLI

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

Tools

100 GitHub tools in Cline CLI

Runlayer policy decides which of these Cline CLI 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 Cline CLI

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Cline 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 before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination