Skip to main content
Book a demo

Connect Assembled to Codex

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

Book a demo Codex setup guide

Set up

Add Assembled to Codex in four steps

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

  1. 1

    Add Assembled to Runlayer

    Assembled isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  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, Assembled’s 13 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 Assembled

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

  4. 4

    Use Assembled from Codex

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

Tools

13 Assembled tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Create forecast adjustments

    Create one or more forecast adjustments layered on the master forecast.

  • Create overtime and voluntary time off

    Publish one overtime ('OT') or voluntary-time-off ('VTO') slot.

  • Get agent time summaries

    Approved overtime (overtime_seconds),

  • Get bpo heatmap

    Get BPO staffing per time bucket: required, committed, scheduled and actuals.

  • Get current time

    Get the current date and time, in both UTC and the company's timezone.

  • Get forecast adjustments

    List existing forecast adjustments for the company.

  • Get forecasted vs actual

    Get forecasted vs actual comparison metrics from Assembled.

  • Get metrics catalog and query usage

    Get the catalog of available metrics and instructions for using the query_metrics() tool.

See all 13 Assembled 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 Assembled 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