# Codex
URL: /integrations/codex

---
title: Codex
sidebarTitle: Codex
description: Give Codex a real cloud browser to drive from the terminal.
llm: true
---

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

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

#### Step 2: Log in

```bash Terminal
steel login
```

#### Step 3: Install the browser skill (recommended)

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

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

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.  Run the task once interactively
2.  Convert it into a script
3.  Schedule 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](/overview/profiles-api/overview) and [Reusing Auth Context](/overview/sessions-api/reusing-auth-context).

### FAQ

### Do I need to write integration code to use Steel with Codex?

No — the integration works through the Steel CLI. Install it with `curl -LsSf https://setup.steel.dev | sh`, run `steel login`, and Codex can start and control Steel sessions, scrape rendered pages, and run computer-use actions from the terminal.

### How does Codex connect to a Steel browser session?

Once Steel CLI is on your `PATH`, Codex inspects command help, runs the commands it needs, and verifies results from the terminal. For better command discovery, install the `steel-browser` skill with `npx skills add steel-dev/skills --skill steel-browser -a codex -g` and restart Codex.

### Does Codex work with Steel's proxies, stealth mode, and CAPTCHA solving?

Yes — those are properties of the Steel session, not of Codex. Sessions started from the CLI run on the same Sessions API that supports `useProxy`, `solveCaptcha`, and `stealthConfig` at creation time.

### How do I turn a one-off Codex browser run into a recurring job?

After a successful manual run, prompt Codex with "Write a bash script based on what you just did", then schedule the script with cron or another runner. The page recommends this run-once, convert, schedule pattern for recurring research, reporting, and monitoring.

### What should I know before pointing Codex at authenticated sites?

Authenticated workflows usually need preconfigured Steel auth state — set up reusable login state via the Profiles API or Reusing Auth Context instead of interactive logins each run. Also note Codex may ask for command approvals depending on your approval mode.


### Resources

*   [Codex + Steel + Resend blog post](https://steel.dev/blog/codex-wired-steel-and-resend-into-a-daily-newsletter) – Example workflow for building a daily newsletter with Codex
*   [Codex CLI docs](https://developers.openai.com/codex/cli) – Install and use Codex locally
*   [Steel CLI docs](/overview/steel-cli) – Full command reference and workflows
*   [Steel Skills](/overview/skills) – Installable skills for coding agents
*   [Steel Discord](https://discord.gg/steel-dev) – Get help and share what you build