---
site: steel.dev
collection: docs
canonical_url: https://steel.dev/docs/integrations/pi
markdown_url: https://steel.dev/docs/integrations/pi.md
content_signal: ai-input=yes, ai-train=yes, search=yes
title: Connect Pi to Steel
description: Give the Pi coding agent a cloud browser with the Steel CLI and its skills, or with the Steel extension for Pi.
summary: Give the Pi coding agent a cloud browser with the Steel CLI and its skills, or with the Steel extension for Pi.
type: integration-guide
reviewed: 2026-11-16
prerequisites: []
related:
  - https://steel.dev/docs/integrations/claude-code.md
  - https://steel.dev/docs/integrations/codex.md
  - https://steel.dev/docs/integrations/cursor.md
  - https://steel.dev/docs/integrations/opencode.md
  - https://steel.dev/docs/integrations/claude.md
agent_setup: https://setup.steel.dev/install.md
docs_index: https://steel.dev/docs/sitemap.md
---

# Connect Pi to Steel

Pi can open pages, click, type and fill forms in a Steel session. Pi runs shell commands, so give it the [Steel CLI](https://steel.dev/docs/control/cli) and the `steel-browser` skill, and it runs `steel` commands in its shell. Or install the Steel extension for Pi, `@steel-dev/pi`. It adds browser tools to Pi, such as `steel_navigate`, `steel_snapshot` and `steel_click`, so Pi drives the browser without shell commands.

## Before you begin

- Pi, installed on your machine. See [pi.dev](https://pi.dev).
- A Steel account. The CLI and the extension sign in with it.
- A project key in the `STEEL_API_KEY` environment variable, if Pi runs unattended. See [API keys](https://steel.dev/docs/account/api-keys).
- For the Steel CLI, macOS or Linux. On Windows, use WSL.
- Node.js 22.20 or later, for the skills installer. The extension needs Node.js 22.19 or later.

## Set up the integration

### Install the CLI and the skill

The prompt in [Set up your agent](https://steel.dev/docs/get-started/agent-setup#1-send-the-setup-prompt) does this step for you: send it to Pi, 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.

```sh
curl -fsS https://setup.steel.dev | sh
```

If you skipped the sign-in, run `steel login`.

If `steel init` did not install the `steel-browser` skill, install it for Pi:

```sh
npx skills add steel-dev/skills --skill steel-browser -a pi -g
```

Restart Pi so that it finds the new skill. `steel skills paths` shows where each skill is installed. To have Pi write Steel code, add the `steel-developer` skill too. [Skills](https://steel.dev/docs/control/skills) lists every skill.

### Add the Steel extension

Use the extension instead of the CLI when you want Pi to call browser tools. Install it with Pi:

```sh
pi install npm:@steel-dev/pi
```

The extension signs in with the Steel CLI's login from `steel login`, or with a project key in `STEEL_API_KEY`. To try it in one run without installing it, start Pi with `pi -e npm:@steel-dev/pi`.

By default, the extension keeps one Steel session open across your prompts. It releases the session when Pi calls `steel_release_session` or when Pi exits. To release the session after each run of the agent, set `STEEL_SESSION_MODE` to `agent`. To release it after each turn, set it to `turn`. The [extension's README](https://github.com/steel-dev/pi-steel) lists every tool and setting.

### Check the connection

With the CLI, check the skill and CLI first:

```sh
steel skills doctor
steel scrape https://example.com
```

`steel scrape` prints the page as Markdown. Then send Pi a first task:

```text
Use Steel to open example.com in a browser, report its title, and stop the session when finished.
```

Pi reports the title **Example Domain**.

With the extension, send Pi a prompt that needs a browser:

```text
Use Steel to open news.ycombinator.com and list the top five stories.
```

Pi calls the `steel_` tools, such as `steel_navigate` and `steel_snapshot`, and lists the stories.

> **Warning**
>
> A session costs browser time until it is released or it times out. With the extension's default mode, the session stays open between your prompts, so ask Pi to release it when you are done.

## Next steps

- [Steel extension for Pi](https://github.com/steel-dev/pi-steel): Every tool of the extension, and the settings for sessions, proxies and CAPTCHAs.
- [We gave Pi agent a real browser](https://steel.dev/blog/we-gave-pi-agent-a-real-browser): How the extension came about, with demo runs.
- [Skills](https://steel.dev/docs/control/skills): Add the skills that debug failed sessions and handle bot detection.
