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 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 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.
- A Steel account. The CLI or the MCP server signs you in with it.
- A project key in the
STEEL_API_KEYenvironment variable, if Codex runs unattended. See 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 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.
curl -fsS https://setup.steel.dev | shIf you skipped the sign-in, run steel login.
If steel init did not install the steel-browser skill, install it for Codex:
npx skills add steel-dev/skills --skill steel-browser -a codex -gRestart Codex so that it finds the new skill. To have Codex write Steel code, add the steel-developer skill too. 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:
[mcp_servers.steel]
url = "https://mcp.steel.dev/mcp"Then sign in:
codex mcp login steelOn 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.
[mcp_servers.steel]
url = "https://mcp.steel.dev/mcp"
bearer_token_env_var = "STEEL_API_KEY"MCP server explains the sign-in, projects and tools.
Check the connection
With the CLI, check the skill and CLI first:
steel skills doctor
steel scrape https://example.comsteel scrape prints the page as Markdown. Then send Codex a first task:
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:
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.
Next steps
- Codex CLI docsInstall Codex and use it on your machine.
- MCP toolsThe tools that Codex calls in a run, with their parameters and results.
- Codex wired Steel and Resend into a daily newsletterCodex scrapes Hacker News with the Steel CLI, emails the stories with Resend, and turns the run into a daily script.