Skip to main content
Book a demo

Connect Ashby ATS to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Ashby ATS 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 Ashby ATS in Runlayer

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

    Cline CLI setup guide
  3. 3

    Sign in to Ashby ATS

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

  4. 4

    Use Ashby ATS from Cline CLI

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

Tools

16 Ashby ATS tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call.

  • Add note to candidate

    Add a note to a candidate's profile.

  • Change application stage

    Move an application to a different interview stage.

  • Consider candidate for job

    Create a new application for a candidate on a specific job.

  • Create candidate

    Create a new candidate record in Ashby with a name and optional contact information.

  • Describe object fields

    Look up filterable fields for a given object type.

  • Filter records

    Filter records of a given object type using a structured JSON filter.

  • Get candidate

    Fetch details about one or more candidates.

  • Get interview details

    Get a detailed interview briefing for a specific Ashby interview event.

See all 16 Ashby ATS 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 Ashby ATS 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