Connect Honeycomb to Codex
Give Codex governed access to Honeycomb’s 38 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Honeycomb to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Add Honeycomb to Runlayer
Honeycomb isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 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, Honeycomb’s 38 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 Honeycomb
Sign in the way Honeycomb requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Honeycomb from Codex
Honeycomb’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
38 Honeycomb tools in Codex
Runlayer policy decides which of these Codex users can call.
Canvas agent invoke
Kick off a single-turn run of the Honeycomb Canvas agent.
Canvas agent poll response
Poll for the result of a previously-issued canvas_agent_invoke call.
Create board
Create a board (dashboard) with query, SLO, and text panels.
Create burn alert
Create a burn alert on an SLO.
Create marker
Creates a marker (a vertical annotation on charts) to mark a point or window in time, such as a deploy, incident, or config change.
Create recipient
Create a notification recipient (email, Slack, PagerDuty, or webhook) so it can be attached to triggers, SLO burn alerts, and Anomaly Detection.
Create slo
Create an SLO (Service Level Objective) backed by an auto-created SLI derived column.
Create trigger
Create a trigger that fires alerts when a query result crosses a threshold.
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 Honeycomb 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