Connect Guru to Codex
Give Codex governed access to Guru’s 6 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Guru to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Guru in Runlayer
Add Guru 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, Guru’s 6 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 Guru
Each user signs in to Guru with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Guru from Codex
Guru’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
6 Guru tools in Codex
Runlayer policy decides which of these Codex users can call. 4 read data only and 1 can change or delete data.
Ask knowledge agent
Generate direct answers to questions using the knowledge base.
Create a draft of content
Create a Draft of a Card in Guru.
Search documents
Find and retrieve specific documents, sources or cards.
Update card content
Update the content of an existing card.
List knowledge agents
Get available knowledge agents and their IDs.
Get Card content by ID
Get full card content in original HTML format by card ID
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 Guru 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