---
site: steel.dev
collection: docs
canonical_url: https://steel.dev/docs/get-started/agent-setup
markdown_url: https://steel.dev/docs/get-started/agent-setup.md
content_signal: ai-input=yes, ai-train=yes, search=yes
title: Set up your agent
description: Send one prompt to your coding agent and watch it drive a Steel cloud browser live, or pick your agent, such as Codex, Pi or Claude, for its own setup.
summary: Send one prompt to your coding agent and watch it browse live, or pick your agent for its own setup.
type: get-started
reviewed: 2026-11-16
prerequisites: []
related:
  - https://steel.dev/docs/get-started/code.md
  - https://steel.dev/docs/get-started/build-your-first-steel-automation.md
  - https://steel.dev/docs/get-started/about-steel.md
agent_setup: https://setup.steel.dev/install.md
docs_index: https://steel.dev/docs/sitemap.md
---

# Set up your agent

Steel gives your agent a cloud browser. The agent opens pages, reads them, clicks, types and fills forms in a Steel session, and you can watch each session live. A coding agent sets itself up from one prompt: it installs the Steel CLI, signs you in, and loads the `steel-browser` skill. To set up a chat agent such as Claude, or one agent step by step, [pick your agent](#pick-your-agent).

## Before you begin

You need:

- A Steel account. Sign up at [app.steel.dev](https://app.steel.dev/sign-up).
- A coding agent that can run shell commands, such as Claude Code, Codex, Cursor, OpenCode or Pi.
- macOS or Linux. On Windows, use WSL.
- Node.js 22.20 or later and git, which the agent uses to install the skill.

You do not need an API key, because the agent signs you in through your browser. The Launch plan is free and includes credits, so you can run this quickstart at no cost. See [Pricing](https://steel.dev/docs/platform/pricing).

## 1. Send the setup prompt

Open your coding agent in the folder of your project, and send it this prompt:

```text
Read https://setup.steel.dev/install.md and follow it to set up Steel for this coding client.
Then continue my requested task using the installed Steel skill.
```

The page at `https://setup.steel.dev/install.md` tells the agent to install the Steel CLI, sign you in, and install the `steel-browser` skill in the project. To give the agent a task in the same message, add the task after the prompt. The Steel dashboard has the same prompt, with a tab for each coding agent.

## 2. Approve the sign-in

The agent gives you a sign-in link. Open it in your browser, approve the sign-in, then tell the agent. The agent finishes the setup and reports what it checked: the CLI version, the sign-in and the skill.

If you sent only the setup prompt, the agent suggests a first task and asks before it starts.

## 3. Watch your agent browse

Send your agent this prompt:

```text
Use Steel to open a browser, send me the live view link, and wait until I say I'm watching. Then open https://steel.dev/practice/news, list the top 3 stories, and stop the session.
```

The agent starts a session and sends you its live view link. Open the link in the browser where you approved the sign-in. It shows the session's browser, live. Tell the agent that you are watching. You see the page open and the agent read it, and the agent then lists the stories and stops the session. After the stop, the same link replays the session.

The `steel-browser` skill teaches the agent to drive the browser with `steel browser` commands. It reads the page as a [snapshot](https://steel.dev/docs/control/snapshots-and-refs), acts on an element by its ref, and reads the page again. [Drive a browser](https://steel.dev/docs/control/cli#drive-a-browser) shows the same commands, to run yourself.

Ask the agent to stop each session when the task is done. A session that the agent leaves open ends by itself when it sits idle or reaches its timeout, as [Set timeouts](https://steel.dev/docs/sessions/timeouts#defaults) shows.

## Pick your agent

Each page sets up one agent step by step, with the Steel CLI and skills or with the MCP server.

- [Claude Code](https://steel.dev/docs/integrations/claude-code): Terminal. The Steel CLI and skills, or the MCP server.
- [Codex](https://steel.dev/docs/integrations/codex): Terminal. The Steel CLI and skills, or the MCP server.
- [Cursor](https://steel.dev/docs/integrations/cursor): Editor. The Steel CLI and skills, or the MCP server.
- [OpenCode](https://steel.dev/docs/integrations/opencode): Terminal. The Steel CLI and skills, or the MCP server.
- [Pi](https://steel.dev/docs/integrations/pi): Terminal. The Steel CLI and skills, or the Steel extension for Pi.
- [Claude](https://steel.dev/docs/integrations/claude): Chat, on the web or in the desktop app. The MCP server, as a custom connector.
- [Any MCP client](https://steel.dev/docs/control/mcp-server#connect-a-client): A client that supports remote MCP servers. One URL and a sign-in.
- [Any agent that reads skills](https://steel.dev/docs/control/skills#install): The Steel CLI and the skills, installed with `npx skills`.

To give a browser to an agent that you build yourself, with a framework such as the Claude Agent SDK, Browser Use or LangGraph, see [Integrations](https://steel.dev/docs/integrations).

## Choose the CLI or the MCP server

- [Steel CLI and skills](https://steel.dev/docs/control/cli): For an agent that runs shell commands. It runs `steel` commands, and the `steel-browser` skill tells it which command fits each step.
- [MCP server](https://steel.dev/docs/control/mcp-server): For an agent without a shell, such as Claude in a chat. Steel hosts the server, so you add one URL and sign in.

[Control interfaces](https://steel.dev/docs/control#mcp-server-and-cli) explains when each one fits.

## Next steps

- [Write Steel code](https://steel.dev/docs/get-started/code): Add the `steel-developer` skill, so that your agent writes Steel programs.
- [Build your first Steel automation](https://steel.dev/docs/get-started/build-your-first-steel-automation): Write a Steel program yourself, step by step, with Playwright.
- [CLI](https://steel.dev/docs/control/cli): Fill forms, run several commands in one request, and run sessions side by side.
- [Skills](https://steel.dev/docs/control/skills): Add the skills that debug a failed session and diagnose bot detection.
- [Examples](https://steel.dev/docs/examples): Start from a runnable project in the Steel cookbook.
