Connect Gumloop to Codex
Give Codex governed access to Gumloop’s 45 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Gumloop to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Gumloop in Runlayer
Add Gumloop 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, Gumloop’s 45 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 Gumloop
Sign in the way Gumloop requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Gumloop from Codex
Gumloop’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
45 Gumloop tools in Codex
Runlayer policy decides which of these Codex users can call.
List agents
List agents in your Gumloop account, with optional search and workspace filtering.
Get agent
Fetch a single Gumloop agent's configuration by its ID.
Ask gummie
Ask questions and get AI-powered answers from Gumloop documentation.
Attach agent MCP server
Attach an MCP server (connector) to a Gumloop agent, or update its configuration if already attached.
Attach agent skills
Attach one or more existing skills to a Gumloop agent.
Call MCP tool
Execute a single tool on a connected MCP server.
Cancel session
Cancel an in-progress Gumloop agent session.
Create agent
Create a new Gumloop agent with a name, model, and optional configuration.
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 Gumloop 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