Solution skill
One-shot scrape? Use quick actions, not a session - and set base_url for self-host
Complete solution
Shows how to fix one-shot scrape? Use quick actions, not a session - and set base_url for self-host. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
And if you self-host steel-browser, set baseURL (Node) or base_url (Python) on the SDK - the default points at Steel Cloud, so a forgotten override sends your traffic to the wrong place.
Steps
- Do not spin up a stateful session for a one-shot scrape - the /scrape, /screenshot, and /pdf quick-action endpoints exist for exactly that and skip session management entirely. Save sessions for multi-step, stateful work where you need cookies and control. And if you self-host steel-browser, set baseURL (Node) or base_url (Python) on the SDK - the default points at Steel Cloud, so a forgotten override sends your traffic to the wrong place.
When to use
You are seeing this: Do not spin up a stateful session for a one-shot scrape - the /scrape, /screenshot, and /pdf quick-action endpoints exist for exactly that and skip session management entirely. Use this skill when you run into "One-shot scrape? Use quick actions, not a session - and set base_url for self-host".
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 browser README: two ways to interact - Sessions for stateful workflows with fine-grained control, and the Quick Actions API (/scrape, /screenshot, /pdf) for simple read-only on-demand jobs. The Node and Python SDKs work against both Steel Cloud and self-hosted steel-browser instances, switching via the baseURL / base_url option.
Verified resolution: Do not spin up a stateful session for a one-shot scrape - the /scrape, /screenshot, and /pdf quick-action endpoints exist for exactly that and skip session management entirely. Save sessions for multi-step, stateful work where you need cookies and control. And if you self-host steel-browser, set baseURL (Node) or base_url (Python) on the SDK - the default points at Steel Cloud, so a forgotten override sends your traffic to the wrong place.
Source URL: https://github.com/steel-dev/steel-browser
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_df621FJo5z2usQNFbPxw8w" 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">One-shot scrape? Use quick actions, not a session - and set base_url for self-host <span>— Vectle</span></a>