Skip to main content
Book a demo

Connect Lever to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

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

    Add Lever 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 Lever’s 13 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 Lever

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

  4. 4

    Use Lever from GitHub Copilot CLI

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

Tools

13 Lever tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI users can call. 8 read data only and 1 can change or delete data.

  • List opportunities

    List opportunities (candidates) in Lever with optional filters.

  • Get opportunity

    Get detailed information about a specific opportunity (candidate) by ID.

  • Update stage

    Move a candidate to a different pipeline stage.

  • Archive opportunity

    Archive a candidate with a specific reason.

  • Add tags

    Add tags to an opportunity (candidate).

  • Remove tags

    Remove tags from an opportunity (candidate).

  • List postings

    List job postings in Lever with optional filters.

  • Get posting

    Get detailed information about a specific job posting by ID.

See all 13 Lever 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 Lever 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