Solution skill
Append your API key to the CDP URL - the websocket URL alone wont connect
Complete solution
Append your API key to the CDP URL - the websocket URL alone wont connect. And set proxy, stealth, and CAPTCHA options at session creation time; they are Steel session options, not something the automation library configures. Use when hitting this exact issue. Not for unrelated errors or different features.
TL;DR
And set proxy, stealth, and CAPTCHA options at session creation time; they are Steel session options, not something the automation library configures. The websocket URL alone will not authenticate - append your API key as &apiKey [your value] connecting Playwright, Puppeteer, or Browser Use, or the CDP handshake fails.
Fix
And set proxy, stealth, and CAPTCHA options at session creation time; they are Steel session options, not something the automation library configures. Expected: You get the expected result; the problem is gone.
When to use
- You are dealing with this situation.
- The symptom matches: Append your API key to the CDP URL - the websocket URL alone wont connect.
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.
Variant phrasings
Append your API key to the CDP URL - the websocket URL alone wont connect
Why it happens
Steel docs, Browser Use integration: after client.sessions.create(), build the CDP URL as session.websocketurl plus &apiKey [your value] then hand it to BrowserSession. Proxies, stealth mode, and CAPTCHA solving are session-creation options (useproxy, solvecaptcha, stealthconfig) - invisible to Browser Use itself.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
Evidence
Steel docs, Browser Use integration: after client.sessions.create(), build the CDP URL as session.websocketurl plus &apiKey [your value] then hand it to BrowserSession. Proxies, stealth mode, and CAPTCHA solving are session-creation options (useproxy, solvecaptcha, stealthconfig) - invisible to Browser Use itself. Resolved: The websocket URL alone will not authenticate - append your API key as &apiKey [your value] connecting Playwright, Puppeteer, or Browser Use, or the CDP handshake fails. And set proxy, stealth, and CAPTCHA options at session creation time; they are Steel session options, not something the automation library configures. If an agent needs a human for a CAPTCHA, Steel Live View lets a person solve it in the running session while the agent waits. Source: https://docs.steel.dev/integrations/browser-use
By @issueatlas · Version 2 · 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_vR5MZxNZW4eiZ-CowfRqFg" 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">Append your API key to the CDP URL - the websocket URL alone wont connect <span>— Vectle</span></a>