Connect Lattice to Codex
Give Codex governed access to Lattice’s 22 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Lattice to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Lattice in Runlayer
Add Lattice 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, Lattice’s 22 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 Lattice
Each user signs in to Lattice with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Lattice from Codex
Lattice’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
22 Lattice tools in Codex
Runlayer policy decides which of these Codex users can call. 15 read data only.
Find ancestors
Find ancestors.
Find employees
Searches for employees in the user's company by name, work email, and/or department.
Find feedback
Retrieves feedback items the user has visibility into.
Find one on ones
Find one on ones.
Find reports
Find reports.
Find reviews
Retrieves reviews the user is permitted to see, filterable by who the review is about, who wrote it, the cycle, direction, submission/sharing status, and date range.
Get current update draft
Returns the user's current-period update draft, with the questions on the form, any answers already saved, the period bounds, and the cadence.
Get draft reviews
Retrieves the open performance review drafts the user is currently authoring.
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 Lattice 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