Connect Omni to Codex
Give Codex governed access to Omni’s 25 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Omni to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Add Omni to Runlayer
Omni isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 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, Omni’s 25 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 Omni
Sign in the way Omni requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Omni from Codex
Omni’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
25 Omni tools in Codex
Runlayer policy decides which of these Codex users can call.
Ask Omni
Starts the full Omni AI agent on an open-ended or multi-step analytical question and returns immediately with a 'jobId' — it does NOT wait for or return the answer, which is retrieved separately once…
Cancel job
Stops a job started by askOmni.
Check dashboard download
Polls a dashboard download started by startDashboardDownload.
Check status
Checks on a job started by askOmni and returns quickly.
Fetch dashboard download
Returns the png a completed dashboard download produced — the job from startDashboardDownload once checkDashboardDownload reports it "complete" — as an image you can look at, after a text block with…
Get app
Alpha — the app content shape may change without a deprecation cycle.
Get app draft
Alpha — the app content shape may change without a deprecation cycle.
Get data
Gets data by generating and executing a query from natural language.
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 Omni 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