Skip to main content
Book a demo

Connect Lever to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

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

    Add Lever 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 Lever’s 13 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

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

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

Tools

13 Lever tools in Cline CLI

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

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

  • Gateway policy (available)

    Every Lever 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