Connect Jam to Codex
Give Codex governed access to Jam’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Jam to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Jam in Runlayer
Add Jam 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, Jam’s 15 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 Jam
Sign in the way Jam requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Jam from Codex
Jam’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
15 Jam tools in Codex
Runlayer policy decides which of these Codex users can call. 13 read data only.
Get Jam bug report details and metadata
Retrieve comprehensive metadata and details for a specific Jam bug report.
Get network activity and HTTP request logs
Extract network activity logs captured during the Jam session.
Get browser console output and javascript logs
Retrieve browser console output captured during the Jam session.
Get user interaction timeline and events
Access the complete timeline of user interactions captured in the Jam.
Get custom Jam metadata
Retrieve custom metadata set via the jam.metadata() SDK.
Get visual screenshots and image attachments
Retrieve visual screenshots and image attachments from screenshot-type Jams.
Analyze video recording
Extract user intents from a Jam recording.
Get video transcript
Retrieve the speech transcript (captions) from a video Jam recording in WebVTT format with timestamps.
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 Jam 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