Connect Vantage to Codex
Give Codex governed access to Vantage’s 157 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Vantage to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Add Vantage to Runlayer
Vantage 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, Vantage’s 157 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 Vantage
Sign in the way Vantage requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Vantage from Codex
Vantage’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
157 Vantage tools in Codex
Runlayer policy decides which of these Codex users can call.
Add team member
Add a user to a Team by email address and assign their Team role.
Create access policy
Create an Access Policy, which limits the costs visible to the Teams it is assigned to.
Create annotation
Create an Annotation on one or more Cost Reports for a specific date.
Create billing rule
Exclusion rules require charge_type.
Create budget
Creates a budget based on the parameters specified.
Create budget alert
Create a Budget Alert that notifies users or connected channels when one or more Budgets reach a percentage threshold during a monthly time window.
Create canvas
Creates a Canvas based on the parameters specified.
Create cost alert
Create a new Cost Alert in Vantage.
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 Vantage 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