Connect Glean to Codex
Give Codex governed access to Glean’s 16 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Glean to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Glean in Runlayer
Add Glean 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, Glean’s 16 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 Glean
Sign in the way Glean requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Glean from Codex
Glean’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
16 Glean tools in Codex
Runlayer policy decides which of these Codex users can call.
Brave actions web search
Searches the web for up-to-date external information from the web.
Chat
AI-powered tool for company knowledge.
Code search
Searches company code and configuration (top matches only).
Create image
Generate a new image from a natural-language prompt using Glean's image generation models, save it as an IMAGE artifact in the user's Library, and return links to view or download it.
Edit image
Modify an existing IMAGE artifact using a natural-language instruction.
Employee search
Finds company employees and their information.
Gmail search
Searches Gmail inbox (Google Workspace) for emails, conversations, and attachments.
Meeting lookup
Searches company calendar meetings and extracts transcripts.
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 Glean 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