---
site: steel.dev
collection: docs
canonical_url: https://steel.dev/docs/integrations/codex
markdown_url: https://steel.dev/docs/integrations/codex.md
content_signal: ai-input=yes, ai-train=yes, search=yes
title: Connect Codex to Steel
description: Give Codex a cloud browser with the Steel CLI and its skills, or with the Steel MCP server.
summary: Give Codex a cloud browser with the Steel CLI and its skills, or with the Steel MCP server.
type: integration-guide
reviewed: 2026-11-12
prerequisites: []
related:
  - https://steel.dev/docs/integrations/claude-code.md
  - https://steel.dev/docs/integrations/cursor.md
  - https://steel.dev/docs/integrations/opencode.md
  - https://steel.dev/docs/integrations/pi.md
  - https://steel.dev/docs/integrations/claude.md
agent_setup: https://setup.steel.dev/install.md
docs_index: https://steel.dev/docs/sitemap.md
---

# Connect Codex to Steel

Codex can open pages, click, type and fill forms in a Steel session. Codex runs shell commands, so give it the [Steel CLI](https://steel.dev/docs/control/cli) and the `steel-browser` skill, and it runs `steel` commands in its shell. If Codex cannot run the `steel` command, for example on Windows without WSL, add the Steel [MCP server](https://steel.dev/docs/control/mcp-server) instead. It gives Codex browser tools, and Steel hosts it, so there is nothing to install. Your Codex approval mode decides whether Codex asks before it runs a command.

## Before you begin

- The Codex CLI, installed on your machine. See the [Codex CLI docs](https://learn.chatgpt.com/docs/codex/cli).
- A Steel account. The CLI or the MCP server signs you in with it.
- A project key in the `STEEL_API_KEY` environment variable, if Codex runs unattended. See [API keys](https://steel.dev/docs/account/api-keys).
- For the Steel CLI, macOS or Linux. On Windows, use WSL.
- Node.js 22.20 or later, for the skills installer.

## Set up the integration

### Install the CLI and the skill

The prompt in [Set up your agent](https://steel.dev/docs/get-started/agent-setup#1-send-the-setup-prompt) does this step for you: send it to Codex, and it installs the CLI and the `steel-browser` skill and signs you in. To do it yourself, install the Steel CLI. In an interactive terminal, the installer then runs `steel init`, which signs you in and installs skills for coding agents.

```sh
curl -fsS https://setup.steel.dev | sh
```

If you skipped the sign-in, run `steel login`.

If `steel init` did not install the `steel-browser` skill, install it for Codex:

```sh
npx skills add steel-dev/skills --skill steel-browser -a codex -g
```

Restart Codex so that it finds the new skill. To have Codex write Steel code, add the `steel-developer` skill too. [Skills](https://steel.dev/docs/control/skills) lists every skill.

### Add the MCP server

Use the MCP server instead of the CLI when Codex cannot run the `steel` command. Add the server to `~/.codex/config.toml`:

```toml file=config.toml
[mcp_servers.steel]
url = "https://mcp.steel.dev/mcp"
```

Then sign in:

```sh
codex mcp login steel
```

On the Steel sign-in page, pick the organization and project. The sessions that Codex creates run in that project.

To skip the sign-in, for example in CI, have Codex send a project key as a bearer token. Codex reads the key from the environment variable that `bearer_token_env_var` names. Sessions then run in the key's project. An organization key does not work, because it is not bound to a project.

```toml file=config.toml
[mcp_servers.steel]
url = "https://mcp.steel.dev/mcp"
bearer_token_env_var = "STEEL_API_KEY"
```

[MCP server](https://steel.dev/docs/control/mcp-server) explains the sign-in, projects and tools.

### Check the connection

With the CLI, check the skill and CLI first:

```sh
steel skills doctor
steel scrape https://example.com
```

`steel scrape` prints the page as Markdown. Then send Codex a first task:

```text
Use Steel to open example.com in a browser, report its title, and stop the session when finished.
```

Codex reports the title **Example Domain**.

With the MCP server, send Codex a prompt that needs a browser:

```text
Use Steel to open news.ycombinator.com and list the top five stories.
```

Codex calls the Steel tools and lists the stories. When it starts a session, the result has a link to watch the session live, in the form `https://app.steel.dev/sessions/SESSION_ID`.

> **Warning**
>
> A session costs browser time until it is released or it times out. Ask Codex to release each session when the task is done.

## Next steps

- [Codex CLI docs](https://learn.chatgpt.com/docs/codex/cli): Install Codex and use it on your machine.
- [MCP tools](https://steel.dev/docs/reference/mcp-tools): The tools that Codex calls in a run, with their parameters and results.
- [Codex wired Steel and Resend into a daily newsletter](https://steel.dev/blog/codex-wired-steel-and-resend-into-a-daily-newsletter): Codex scrapes Hacker News with the Steel CLI, emails the stories with Resend, and turns the run into a daily script.
