Skip to main content
Book a demo

Connect Grain to Codex

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

Book a demo Codex setup guide

Set up

Add Grain to Codex in four steps

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

  1. 1

    Approve Grain in Runlayer

    Add Grain 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, Grain’s 15 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 Grain

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

  4. 4

    Use Grain from Codex

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

Tools

15 Grain tools in Codex

Runlayer policy decides which of these Codex users can call. 15 read data only.

  • Myself

    Get information about the logged-in Grain user.

  • List meetings

    Returns a filtered list of Grain meetings you have access to, ordered by most recent.

  • List attended meetings

    Returns a filtered list of Grain meetings you have attended, ordered by most recent.

  • Fetch meeting

    Fetches information about a single Grain meeting by ID.

  • Fetch meeting notes

    Fetches the AI notes payload from a single Grain meeting by ID.

  • Fetch meeting transcript

    Fetches the transcript from a single Grain meeting by ID.

  • Search persons

    Returns a filtered list of persons that were participants of Grain meetings you have access to.

  • Search companies

    Returns a filtered list of companies that were participants of Grain meetings you have access to.

See all 15 Grain 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 Grain 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