Skip to main content
Book a demo

Connect Nimble to Codex

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

Book a demo Codex setup guide

Set up

Add Nimble to Codex in four steps

Admins approve the server once. Everyone in Codex then gets it through the same governed connection.

  1. 1

    Approve Nimble in Runlayer

    Add Nimble 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, Nimble’s 27 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 Nimble

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

  4. 4

    Use Nimble from Codex

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

Tools

27 Nimble tools in Codex

Runlayer policy decides which of these Codex users can call. 16 read data only and 5 can change or delete data.

  • Nimble crawl run

    Nimble Crawl: one-time bulk fetch of a known doc tree or URL list.

  • Nimble crawl status

    Check the status and progress of a running or completed crawl job.

  • Nimble crawl list

    List crawl jobs, optionally filtered by status.

  • Nimble crawl terminate

    Cancel a running or queued crawl job.

  • List extraction templates

    Browse Extraction Templates — reusable, site-specific structured scrapers.

  • Get extraction template

    Get an Extraction Template's input/output schema before running it.

  • Run extraction template

    Run an Extraction Template against 1–few known items (URL or site ID).

  • Generate extraction template

    Generate a new Extraction Template — only when the user explicitly asks to.

See all 27 Nimble 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 Nimble 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