Skip to main content
Book a demo

Connect Ashby ATS to Codex

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

Book a demo Codex setup guide

Set up

Add Ashby ATS to Codex in four steps

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

    Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Ashby ATS’s 16 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex 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 Codex

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

Tools

16 Ashby ATS tools in Codex

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

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

  • Gateway policy (available)

    Every Ashby ATS call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

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

  • Block output after it runs (available)

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

  • Redact output in place (not available)

    Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination