Skip to main content
Book a demo

Connect Pendo to Codex

Give Codex governed access to Pendo’s 54 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Codex setup guide

Set up

Add Pendo to Codex in four steps

Admins approve the server once. Everyone in Codex then gets it through the same governed connection.

  1. 1

    Approve Pendo in Runlayer

    Add Pendo from the catalog and choose who can use it and which of its tools are allowed.

  2. 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, Pendo’s 54 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex setup guide
  3. 3

    Sign in to Pendo

    Sign in the way Pendo requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Pendo from Codex

    Pendo’s approved tools appear in Codex. Every call is checked against policy and recorded.

Tools

54 Pendo tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Account metadata schema

    Return the set of metadata fields available for accounts.

  • Acquisition trend

    Count new visitors or accounts per period - users whose first-ever interaction with the app (scope='app'), a specific page or feature (scope='page' or 'feature'), or a track event…

  • Agent analytics conversation analysis

    Lists and ranks individual AI agent conversations with per-conversation metrics.

  • Agent analytics issue analysis

    Returns issue diagnoses, flagged response tool/model usage, and user prompt content for the events of a specific detected issue cluster in AI Agent Analytics.

  • Agent analytics key metrics

    Returns key aggregate metrics for AI agent conversations with period-over-period comparison.

  • Agent analytics tracked issue analysis

    Deep-dives into a single tracked issue in AI Agent Analytics for a specific AI agent, surfacing the visitors and accounts, sampled issue explanations from detected issue clusters, the tools and…

  • Agent analytics tracked use case analysis

    Deep-dives into a single tracked use case in AI Agent Analytics for a specific AI agent, surfacing the visitors and accounts, the tools and models the agent invoked, sampled explanations, and a…

  • Aggregate entity usage

    Rank pages, features, or track events by aggregate usage over a date range, or measure a named set of them as one population.

See all 54 Pendo tools

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 Pendo 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

Find another combination