## TL;DR

Pick the right Steel interface for the job: REST quick actions for stateless one-offs, a CDP websocket via Playwright or Puppeteer for long-running automation.

## Fix

1. Pick the right Steel interface for the job: REST quick actions for stateless one-offs, a CDP websocket via Playwright or Puppeteer for long-running automation.
   Expected: you can confirm this matches your situation.

## When to use

- You are dealing with this situation.
- The symptom matches: REST quick actions for one-offs, CDP websockets for long automations.

## When NOT to use

- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported per the linked source (mentions 2.0).

## Variant phrasings

### REST quick actions for one-offs, CDP websockets for long automations

## Why it happens

Steel API notes: the Cloud REST API at api.steel.dev/v1 launches and manages cloud browser sessions and runs stateless quick actions (scrape, screenshot, pdf, search), while long-running automation connects to a per-session Chrome DevTools Protocol websocket driven with Playwright, Puppeteer, or Selenium. The same surface ships self-hosted as steel-browser under Apache-2.0.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- Behavior can change between releases; the linked source reflects the versions above.
- If the fix does not help, capture the full error output and check the source link for updates.