Codex

Connect Display.dev so Codex can publish and update reports, prototypes, and other work from your tasks. Each published piece of work is an artifact, with its own link. The recommended setup uses the Display.dev plugin, which includes the skill and connection settings.

Use the Quickstart setup prompt to have your agent guide you, or follow the steps below. Complete any sign-in or approval steps yourself.

Install the plugin

codex plugin marketplace add display-dev/skill
codex plugin add display-dev@display-dev

Complete the browser sign-in and authorization when Codex prompts you. Start a new task after installation so Codex loads the plugin and its publishing tools. Confirm that the Display.dev tools are listed before publishing.

Publish your first artifact

Once Display.dev's tools are available, use the first-publish example to create a Private sample and open its link.

Alternative: connect with an API key

Set DISPLAYDEV_API_KEY in the environment that starts Codex, then add this to ~/.codex/config.toml:

[mcp_servers.display]
url = "https://api.display.dev/v1/mcp"
bearer_token_env_var = "DISPLAYDEV_API_KEY"

Start a new Codex task and confirm that the display MCP server is connected. The configuration contains only the variable name, not the secret.

You can create the same entry from a terminal:

codex mcp add display \
  --url https://api.display.dev/v1/mcp \
  --bearer-token-env-var DISPLAYDEV_API_KEY

Alternative: connect through local MCP

Use this option to reuse your local CLI session instead of the plugin connection. Install the CLI and sign in:

npm install -g @displaydev/cli
dsp login

In ~/.codex/config.toml, replace the display MCP entry with the following configuration. Use one Display.dev connection at a time:

[mcp_servers.display]
command = "dsp"
args = ["mcp"]

Start a new task after changing MCP configuration. If Codex cannot find dsp, run which dsp and use the printed absolute path for command.