Connect AirOps to Codex
Give Codex governed access to AirOps’s 100 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add AirOps to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve AirOps in Runlayer
Add AirOps 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, AirOps’s 100 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 AirOps
Sign in the way AirOps requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use AirOps from Codex
AirOps’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
100 AirOps tools in Codex
Runlayer policy decides which of these Codex users can call.
Accept opportunity
Accept pending opportunities for a campaign and add them to the campaign action grid.
Add AEO region
Add a region (ISO alpha-2 country code) to a Brand Kit's configured AEO regions.
Add grid column
Add a new column to a grid table.
Analytics chart
Query analytics data and display it as an interactive chart.
Automated feedback report
AirOps only feedback tool.
Bulk update AEO prompt tags
Apply a single tag operation (add or remove) to a batch of AEO prompts in one Brand Kit, atomically.
Bulk update AEO prompt topics
Reassign a batch of AEO prompts to an existing topic in one Brand Kit.
Commit AEO prompt assignments
Commit the current prompt-assignment draft for a Brand Kit to live.
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 AirOps 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