Skip to main content
Book a demo

Connect Salesforce DX to Codex

Give Codex governed access to Salesforce DX through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Codex setup guide

Set up

Add Salesforce DX to Codex in four steps

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

  1. 1

    Approve Salesforce DX in Runlayer

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

  2. 2

    Connect Codex to Runlayer

    Install the Runlayer CLI so Codex can reach Salesforce DX, which runs on the user’s machine. Auto Sync can then write Salesforce DX into Codex on macOS, Windows, and Linux.

    Codex setup guide
  3. 3

    Sign in to Salesforce DX

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

  4. 4

    Use Salesforce DX from Codex

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

Tools

Salesforce DX tools in Codex

Salesforce DX reports its tools when your organization connects it, so the list depends on your deployment.

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 Salesforce DX 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