# Claude Code
URL: /integrations/claude-code

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

The Claude Code integration gives Claude Code a real cloud browser through the Steel CLI. From a Claude Code session, you can start and control Steel sessions, scrape rendered pages, run computer-use actions, watch live browser state through the session viewer, and turn successful runs into repeatable scripts.

Claude Code already works well with shell commands; Steel adds the browser surface for sites that need JavaScript, session state, or interactive navigation.

### Requirements

*   **Node.js**: Version 18 or higher
*   **Claude Code**: 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 Claude Code better command discovery and more reliable browser workflows.

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

Restart Claude Code after installing so it can discover the skill.

### Authenticated workflows

For authenticated sites, prepare reusable auth state in Steel ahead of time rather than asking Claude Code to handle login from scratch during every run.

See:

*   [Profiles API](/overview/profiles-api/overview)
*   [Reusing Auth Context](/overview/sessions-api/reusing-auth-context)

### Live debugging

Steel sessions return a viewer URL that makes it easier to monitor what the agent is doing in real time. This is useful when Claude Code reaches a modal, a sign-in wall, or a page that does not behave as expected.

### Repeatable workflows

After a successful run, Claude Code can help turn the browser workflow into something more repeatable:

*   A bash script for local execution
*   A project-specific command or workflow
*   A documented runbook for recurring tasks

### Constraints

*   **Command approvals depend on your Claude Code settings.** Shell access may require approval depending on your permission mode.
*   **First runs are usually the roughest.** Dynamic web apps often need a few retries before the workflow is stable.
*   **Authenticated sites work best with prepared Steel auth state.** Reusing profiles or auth context is generally more reliable than repeated interactive logins.

### FAQ

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

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

### How does Claude Code connect to a Steel browser session?

Through Steel CLI commands in its shell. For better command discovery and more reliable workflows, install the `steel-browser` skill with `npx skills add steel-dev/skills --skill steel-browser -a claude-code -g` and restart Claude Code so it discovers the skill.

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

Yes — those are properties of the Steel session itself, not the client driving it. Sessions Claude Code starts run on the same Sessions API that supports `useProxy`, `solveCaptcha`, and `stealthConfig` at creation time.

### How should I handle sites that require login?

Prepare reusable auth state in Steel ahead of time via the Profiles API or Reusing Auth Context, rather than asking Claude Code to log in from scratch every run. The page calls prepared auth state more reliable than repeated interactive logins.

### Can I watch what Claude Code is doing in the browser?

Yes — Steel sessions return a viewer URL for monitoring the browser in real time. That's especially useful when Claude Code hits a modal, a sign-in wall, or a page that misbehaves, and successful runs can then be turned into scripts or runbooks.


### Resources

*   [Give Claude Code a real browser](https://steel.dev/blog/give-claude-code-a-real-browser) – Blog post on using Claude Code with Steel
*   [Claude Code overview](https://code.claude.com/docs/en/overview) – Official Claude Code documentation
*   [How Claude Code works](https://code.claude.com/docs/en/how-claude-code-works) – Built-in tools, permissions, and execution model
*   [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