Skip to main content
Book a demo

Connect Devin to Codex

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

Book a demo Codex setup guide

Set up

Add Devin to Codex in four steps

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

  1. 1

    Add Devin to Runlayer

    Devin 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, Devin’s 24 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 Devin

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

  4. 4

    Use Devin from Codex

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

Tools

24 Devin tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Ask wiki question

    Ask any question about a GitHub repository's codebase and get an AI-powered answer grounded in its DeepWiki.

  • Automation manage

    Manage Devin automations.

  • Billing tag manage

    Manage Devin billing tags (groupings of Devin sessions for usage tracking) with a single action-based tool: list/get/create tags, assign sessions one at a time or in bulk (up to 500 per call, sent in…

  • Blueprint test

    Test a candidate blueprint YAML in an authoring VM: start → run initialize → fix → run initialize again (clean VM) → run maintenance → then persist with update_environment_config.

  • Campaign manage

    Read and publish a bot's campaign: its plan, its append-only readings and its status.

  • Code scan manage

    Manage Devin code scans (sometimes referred to as "security scans" or "Devin Security Swarm").

  • Find setting

    Find a Devin webapp setting and get a deep-link URL to it.

  • Knowledge manage

    Manage Devin knowledge notes and suggestions via a single action-based tool.

See all 24 Devin 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 Devin 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