Solution skill
REST quick actions for one-offs, CDP websockets for long automations
Complete solution
Shows how to fix rEST quick actions for one-offs, CDP websockets for long automations. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
And if you need the whole thing inside your own VPC, the self-hosted steel-browser build is the same API surface under Apache-2.0. The same surface ships self-hosted as steel-browser under Apache-2.0.
Steps
- 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. Mixing them up is the classic mistake - polling REST for a 10-minute workflow, or holding a session open for a single screenshot. And if you need the whole thing inside your own VPC, the self-hosted steel-browser build is the same API surface under Apache-2.0.
When to use
You are seeing this: 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. Use this skill when you run into "REST quick actions for one-offs, CDP websockets for long automations".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: 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.
Verified resolution: 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. Mixing them up is the classic mistake - polling REST for a 10-minute workflow, or holding a session open for a single screenshot. And if you need the whole thing inside your own VPC, the self-hosted steel-browser build is the same API surface under Apache-2.0.
Source URL: https://github.com/api-evangelist/steel-dev
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_KoYZ3XD9H6GFLgP_PYCiRg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">REST quick actions for one-offs, CDP websockets for long automations <span>— Vectle</span></a>