Immutable solution version
Hyperbrowser session dies on disconnect - add &keepAlive=true to the wsEndpoint to keep it alive
Complete solution
Hyperbrowser session dies on disconnect - add &keepAlive=true to the wsEndpoint to keep it alive. If your Hyperbrowser session keeps dying when your script disconnects, that is the default behavior - disconnecting over CDP stops the session. Use when hitting this exact issue. Not for unrelated errors or different features.
TL;DR
If your Hyperbrowser session keeps dying when your script disconnects, that is the default behavior - disconnecting over CDP stops the session. Append &keepAlive=true to the wsEndpoint when you connect and the session survives disconnects, living until its timeoutMinutes value or until you explicitly stop it.
Fix
If your Hyperbrowser session keeps dying when your script disconnects, that is the default behavior - disconnecting over CDP stops the session. Expected: You get the expected result; the problem is gone.
When to use
- You are dealing with this situation.
- The symptom matches: Hyperbrowser session dies on disconnect - add &keepAlive=true to the wsEndpoint to keep it alive.
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. Source: https://hyperbrowser.ai/docs/sessions/lifecycle.md.
Variant phrasings
Hyperbrowser session dies on disconnect - add &keepAlive=true to the wsEndpoint to keep it alive
Why it happens
Hyperbrowser's official session lifecycle docs: when you disconnect from a session via Playwright or Puppeteer, the session automatically stops. To keep it alive across disconnects, add the &keepAlive=true query parameter to the session's WebSocket endpoint when connecting over CDP. The session then stays alive until its timeout (default team setting or the timeoutMinutes passed at creation) or until you stop it via the API.
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.
Source
https://hyperbrowser.ai/docs/sessions/lifecycle.md
Evidence
Source: Hyperbrowser's official session lifecycle docs: when you disconnect from a session via Playwright or Puppeteer, the session automatically stops. To keep it alive across disconnects, add the &keepAlive=true query parameter to the session's WebSocket endpoint when connecting over CDP. The session then stays alive until its timeout (default team setting or the timeoutMinutes passed at creation) or until you stop it via the API.
Verified resolution: If your Hyperbrowser session keeps dying when your script disconnects, that is the default behavior - disconnecting over CDP stops the session. Append &keepAlive=true to the wsEndpoint when you connect and the session survives disconnects, living until its timeoutMinutes value or until you explicitly stop it. Useful for multi-step pipelines where your process reconnects later to the same browser.
Source URL: https://hyperbrowser.ai/docs/sessions/lifecycle.md
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_mKgXU1TtaWYMok2yYdA_jg" 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">Hyperbrowser session dies on disconnect - add &keepAlive=true to the wsEndpoint to keep it alive <span>— Vectle</span></a>