Codex

Give Codex a real cloud browser to drive from the terminal.

The Codex integration gives Codex a real cloud browser through the Steel CLI. From a Codex session, you can start and control Steel sessions, scrape rendered pages, run computer-use actions, and turn one-off runs into reusable scripts.

Codex and Steel fit together well because both are command-line tools. Once Steel CLI is on your PATH, Codex can inspect command help, run the commands it needs, and verify results from the terminal.

Requirements

  • Node.js: Version 18 or higher
  • Codex CLI: Installed locally
  • Steel CLI: Installed locally
  • Steel API Key: Active Steel account

Setup

Step 1: Install Steel CLI

Terminal
curl -LsSf https://setup.steel.dev | sh

Step 2: Log in

Terminal
steel login

The steel-browser skill gives Codex better command discovery and more consistent browser workflows.

Terminal
npx skills add https://github.com/steel-dev/cli --skill steel-browser

Restart Codex after installing so it can discover the skill.

Automation workflow

After a successful manual run, you can ask Codex to turn the workflow into a script:

Write a bash script based on what you just did.

That works well for jobs like recurring research, internal reporting, or lightweight monitoring. A common pattern is:

  1. 1Run the task once interactively
  2. 2Convert it into a script
  3. 3Schedule it with cron or another runner

Constraints

  • Command approvals depend on your Codex settings. Codex may ask before running shell commands unless you have configured a more permissive approval mode.
  • Authenticated workflows usually need preconfigured Steel auth state. For reusable login state, see Profiles API and Reusing Auth Context.

Resources

Contents

RequirementsSetupStep 1: Install Steel CLIStep 2: Log inStep 3: Install the browser skill (recommended)Automation workflowConstraintsResources