Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.corridor.dev/llms.txt

Use this file to discover all available pages before exploring further.

Corridor integrates with OpenAI Codex via MCP and hooks, ensuring that code generated by the Codex CLI is checked against your security guardrails.

​
Prerequisites

  • OpenAI Codex CLI installed (codex command available in PATH)
  • A Corridor account with a team created

​
Setup

1

Install the Corridor CLI

Install the Corridor CLI with a single command:
curl -fsSL https://app.corridor.dev/cli/install.sh | bash
The CLI auto-updates on startup, so you’ll always have the latest version.The installer runs corridor install automatically, detects the codex binary in PATH, and sets up the Corridor plugin, MCP server, hooks, and agent rules for Codex. The installer simultaneously installs and updates Corridor for all supported CLI tools (including Claude Code and Factory). Run this one time to install Corridor across all of these agents. You will need to re-run the installer again if you download a new agent.
2

Verify the plugin

Restart Codex if it’s currently running. You can verify the MCP server is connected by running /mcp inside Codex.
Once configured, Codex will invoke Corridor’s security checks as it writes code, catching vulnerabilities and enforcing your security policies automatically.

​
Hooks

Hooks are deterministic scripts that run at specific points in the code generation process, enabling real-time security reviews and policy enforcement.
Codex hooks are currently supported on macOS only. On Linux and Windows, the MCP server still runs and provides guardrails, but hook-based stop checks are skipped because Codex has no per-user managed-hooks path on those platforms.

​
MCP compliance

Corridor tracks which MCP servers are active and enforces your team’s policies. To configure, navigate to the Compliance tab in the Corridor dashboard and choose Allowlist Mode or Blocklist Mode.

​
Troubleshooting hooks

If hooks are not running:
  • Run corridor install --force to reinstall the plugin and refresh the managed hooks payload.
  • On macOS, confirm the managed hooks key is present: 
    defaults read com.openai.codex requirements_toml_base64

​
Uninstalling

To remove the Corridor CLI and all its configuration, run the uninstall script: 
curl -fsSL https://app.corridor.dev/cli/uninstall.sh | bash

​
Next steps

Guardrails

Learn how guardrails protect your code

Corridor MCP

Explore Corridor’s MCP tools