Connect Cloudflare AI Gateway to Codex
Give Codex governed access to Cloudflare AI Gateway through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Cloudflare AI Gateway to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Cloudflare AI Gateway in Runlayer
Add Cloudflare AI Gateway from the catalog and choose who can use it and which of its tools are allowed.
- 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, Cloudflare AI Gateway’s tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex setup guide - 3
Sign in to Cloudflare AI Gateway
Sign in the way Cloudflare AI Gateway requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Cloudflare AI Gateway from Codex
Cloudflare AI Gateway’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
Cloudflare AI Gateway tools in Codex
Cloudflare AI Gateway reports its tools when your organization connects it, so the list depends on your deployment.
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 Cloudflare AI Gateway 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