Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
69 changes: 42 additions & 27 deletions components/home/cli-install-card.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,11 @@ import * as React from 'react';
import { cn } from '@/lib/utils';

const CLI_INSTALL_COMMAND = 'curl -fsS https://setup.steel.dev | sh';
const AGENT_SETUP_PROMPT =
'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.';

export function CLIInstallCard() {
const [copied, setCopied] = React.useState(false);
const [copied, setCopied] = React.useState<string | null>(null);

return (
<div className="relative block rounded-lg bg-border p-[1.5px]">
Expand All @@ -18,32 +20,45 @@ export function CLIInstallCard() {
Install Steel CLI and the steel-browser skill so your agent can control a browser.
</p>
</div>
<button
type="button"
aria-label={`Copy command: ${CLI_INSTALL_COMMAND}`}
className={cn(
'flex w-full cursor-pointer items-center gap-2 rounded-lg border px-3 py-[7px]',
'font-mono text-[12.5px] text-foreground transition-colors',
copied
? 'border-primary/30 bg-primary/5'
: 'border-border bg-background hover:border-primary/30 hover:bg-accent/30',
)}
onClick={() => {
navigator.clipboard.writeText(CLI_INSTALL_COMMAND);
setCopied(true);
setTimeout(() => setCopied(false), 1200);
}}
>
<span className="select-none text-muted-foreground/50">$</span>
<span className="min-w-0 flex-1 overflow-x-auto text-left whitespace-nowrap [scrollbar-width:none] [-ms-overflow-style:none] [&::-webkit-scrollbar]:hidden">
{CLI_INSTALL_COMMAND}
</span>
{copied ? (
<Check className="h-3.5 w-3.5 shrink-0 text-muted-foreground/70" aria-hidden="true" />
) : (
<Copy className="h-3.5 w-3.5 shrink-0 text-muted-foreground/50" aria-hidden="true" />
)}
</button>
{[
{ label: 'Run in your terminal', text: CLI_INSTALL_COMMAND },
{ label: 'Paste into your coding agent', text: AGENT_SETUP_PROMPT },
].map(({ label, text }) => (
<div key={label} className="space-y-2">
<p className="text-sm text-muted-foreground">{label}</p>
<button
type="button"
aria-label={`Copy: ${label}`}
className={cn(
'flex w-full cursor-pointer items-center gap-2 rounded-lg border px-3 py-[7px]',
'font-mono text-[12.5px] text-foreground transition-colors',
copied === label
? 'border-primary/30 bg-primary/5'
: 'border-border bg-background hover:border-primary/30 hover:bg-accent/30',
)}
onClick={() => {
navigator.clipboard.writeText(text);
setCopied(label);
setTimeout(() => setCopied(null), 1200);
}}
>
<span className="min-w-0 flex-1 whitespace-pre-wrap break-words text-left">
{text}
</span>
{copied === label ? (
<Check
className="h-3.5 w-3.5 shrink-0 text-muted-foreground/70"
aria-hidden="true"
/>
) : (
<Copy
className="h-3.5 w-3.5 shrink-0 text-muted-foreground/50"
aria-hidden="true"
/>
)}
</button>
</div>
))}
</div>
</div>
);
Expand Down
46 changes: 32 additions & 14 deletions content/docs/integrations/claude-code.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,34 +11,48 @@ Claude Code already works well with shell commands; Steel adds the browser surfa

### Requirements

* **Node.js**: Version 18 or higher
* **Node.js/npm**: Including `npx` for skill installation
* **Claude Code**: Installed locally
* **Steel CLI**: Installed locally
* **Steel API Key**: Active Steel account
* **Steel CLI**: Stable v0.5.0 or later (installed during setup)
* **Steel account**: Device authorization; no API-key copy required

### Setup

#### Step 1: Install Steel CLI
#### Step 1: Ask Claude Code to set up Steel

```bash Terminal
curl -LsSf https://setup.steel.dev | sh
Paste this into Claude Code:

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

#### Step 2: Log in
The guide installs the stable binary and initializes the correct skill target:

```bash Terminal
steel login
curl -fsSL https://setup.steel.dev/install.sh | sh -s -- --non-interactive
"$HOME/.steel/bin/steel" --json init --agent --from claude-code
```

#### Step 3: Install the browser skill (recommended)
#### Step 2: Approve and resume

The `steel-browser` skill gives Claude Code better command discovery and more reliable browser workflows.
Open the device authorization URL returned by Steel and approve it in your own
browser. Tell Claude Code when approval is complete so it reruns the same command:

```bash Terminal
npx skills add steel-dev/skills --skill steel-browser -a claude-code -g
"$HOME/.steel/bin/steel" --json init --agent --from claude-code
```

#### Step 3: Load the browser skill

Targeted init installs `steel-browser`. Ask Claude Code to load it through its
native skill mechanism, then continue the task you requested:

```text Prompt
Load the installed steel-browser skill, perform my browser task, verify the result, and stop the session you created when finished.
```

Restart Claude Code after installing so it can discover the skill.
Skill installation, skill loading, and first-task completion are separate
checks. Reload the client if its skill discovery requires it.

### Authenticated workflows

Expand Down Expand Up @@ -72,11 +86,15 @@ After a successful run, Claude Code can help turn the browser workflow into some
:::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.
No. Follow the [agent setup guide](https://setup.steel.dev/install.md) with
`claude-code` as the target. After device approval and skill loading, Claude Code
can operate Steel browser sessions through the CLI.

### 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.
Through Steel CLI commands in its shell. The CLI uses the HTTP Commands API for
browser actions. Targeted init installs `steel-browser`; load the skill before
running the task.

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

Expand Down
46 changes: 32 additions & 14 deletions content/docs/integrations/codex.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,34 +11,48 @@ Codex and Steel fit together well because both are command-line tools. The same

### Requirements

* **Node.js**: Version 18 or higher
* **Node.js/npm**: Including `npx` for skill installation
* **Codex CLI**: Installed locally
* **Steel CLI**: Installed locally
* **Steel API Key**: Active Steel account
* **Steel CLI**: Stable v0.5.0 or later (installed during setup)
* **Steel account**: Device authorization; no API-key copy required

### Setup

#### Step 1: Install Steel CLI
#### Step 1: Ask Codex to set up Steel

```bash Terminal
curl -LsSf https://setup.steel.dev | sh
Paste this into Codex:

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

#### Step 2: Log in
The guide installs the stable binary and initializes the correct skill target:

```bash Terminal
steel login
curl -fsSL https://setup.steel.dev/install.sh | sh -s -- --non-interactive
"$HOME/.steel/bin/steel" --json init --agent --from codex
```

#### Step 3: Install the browser skill (recommended)
#### Step 2: Approve and resume

The `steel-browser` skill gives Codex better command discovery and more consistent browser workflows.
Open the device authorization URL returned by Steel and approve it in your own
browser. Tell Codex when approval is complete so it reruns the same command:

```bash Terminal
npx skills add steel-dev/skills --skill steel-browser -a codex -g
"$HOME/.steel/bin/steel" --json init --agent --from codex
```

#### Step 3: Load the browser skill

Targeted init installs `steel-browser`. Ask Codex to read the installed skill
through its native skill mechanism before continuing your task:

```text Prompt
Load the installed steel-browser skill, perform my browser task, verify the result, and stop the session you created when finished.
```

Restart Codex after installing so it can discover the skill.
Skill installation, skill loading, and first-task completion are separate
checks. Reload the client if its skill discovery requires it.

### Automation workflow

Expand All @@ -64,11 +78,15 @@ That works well for jobs like recurring research, internal reporting, or lightwe
:::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.
No. Follow the [agent setup guide](https://setup.steel.dev/install.md) with
`codex` as the target. After device approval and skill loading, Codex can operate
Steel browser sessions through the CLI.

### 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.
Through Steel CLI commands in its shell. The CLI uses the HTTP Commands API for
browser actions. Targeted init installs `steel-browser`; load the skill before
running the task.

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

Expand Down
18 changes: 14 additions & 4 deletions content/docs/integrations/openclaw.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,14 @@ Good fit for application forms, operational workflows, and browser-driven resear
* **Node.js**: Version 18 or higher
* **OpenClaw**: Installed locally
* **Steel CLI**: Installed locally
* **Steel API Key**: Active Steel account
* **Steel account**: Device authorization or an API key

### Setup

OpenClaw is separate from OpenCode. It is not a supported
`steel init --agent --from` target in v0.5.0. Use the manual setup below rather
than selecting `opencode` for OpenClaw.

#### Step 1: Install Steel CLI

```bash Terminal
Expand All @@ -35,10 +39,14 @@ steel login
The `steel-browser` skill gives OpenClaw better command discovery and more reliable browser workflows.

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

Restart OpenClaw after installing so it can discover the skill.
Choose OpenClaw if your skill installer offers it. Otherwise, follow OpenClaw's
manual skill-installation instructions for the
[steel-browser skill](https://github.com/steel-dev/skills/tree/main/steel-browser).
Do not install into OpenCode's directories as a substitute. Load the installed
skill through OpenClaw's skill mechanism before running a task.

### Example workflow

Expand Down Expand Up @@ -96,7 +104,9 @@ No — the integration works through the Steel CLI. Install it with `curl -LsSf

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

Via Steel CLI commands in its shell. Install the `steel-browser` skill for better command discovery — `npx skills add steel-dev/skills --skill steel-browser -a opencode -g` — then restart OpenClaw so it discovers the skill.
Via Steel CLI commands in its shell. Install `steel-browser` using OpenClaw's
skill mechanism, then load it before running a task. OpenClaw and OpenCode are
different clients; the `opencode` installation target is not an OpenClaw alias.

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

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ llm: true

## Install

For complete stable CLI setup, device authorization, and targeted installation,
follow [the agent onboarding guide](https://setup.steel.dev/install.md).
To install only this skill:

```bash Terminal
npx skills add steel-dev/skills --skill steel-browser
```
Expand All @@ -17,6 +21,9 @@ After adding the Steel Skills marketplace in Claude Code:
/plugin install steel-browser@steel-skills
```

Load the installed skill through your client's native skill mechanism before
using it. Installation alone is not evidence that the skill has been loaded.

## Use When

- The agent should visit a page now.
Expand Down
15 changes: 14 additions & 1 deletion content/docs/overview/skills/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,13 @@ Most users should start with `steel-browser` and `steel-developer`. Add the debu

## Quick install

For complete CLI authorization and browser-skill setup in OpenCode, Codex, Pi,
or Claude Code, start with the [agent onboarding guide](https://setup.steel.dev/install.md):

```text Prompt
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.
```

Use `npx skills` when you want a direct install command that works across supported coding agents.

```bash Terminal
Expand Down Expand Up @@ -61,6 +68,10 @@ npx skills add steel-dev/skills --skill steel-browser -a opencode -g

Supported agent targets are Claude Code, Cursor, Codex, OpenCode, and Pi.

These are standalone skill-installer targets. The stable CLI's targeted
`init --agent --from` flow currently accepts only `claude-code`, `codex`,
`opencode`, and `pi`; it does not accept `cursor`.

## Which skill should I use?

- Use `steel-browser` for live web work the agent should perform now.
Expand All @@ -77,7 +88,9 @@ steel doctor --preflight
steel scrape https://example.com
```

Restart your agent client after installing new skills so it can discover them.
Load the installed skill using your client's skill mechanism; reload or restart
the client if its discovery requires it. A successful install or doctor check
does not establish skill loading or completion of your requested task.

## Skills or MCP?

Expand Down
Loading
Loading