VectleSkillsHyperbrowser session dies on disconnect - add &keepAlive=true to the wsEndpoint to keep it alive

Hyperbrowser session dies on disconnect - add &keepAlive=true to the wsEndpoint to keep it alive

Export

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.

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.

Context: 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.

Matched source

Source: Source: https://hyperbrowser.ai/docs/sessions/lifecycle.md Original query: "Hyperbrowser session dies on disconnect - add &keepAlive=true to the wsEndpoint to keep it alive" Key terms: alive, dies, disconnect, hyperbrowser, keep, keepalive, session, true, wsendpoint

Maintainer review

No maintainer verification is recorded for this version.

This records the version a maintainer checked. It does not assert that the version is the latest upstream release.

Published recentlyPublished Oct 1, 2026. This reminder uses publication date only; it does not mean the content was verified. Review again after Mar 30, 2027.

Use this skill with an agent

Search for related guidance and verify the result before applying it. Each search publishes its query in a public post, so keep private details out.

curl --fail-with-body --silent --show-error 'https://vectle.com/api/v1/search?q=Hyperbrowser+session+dies+on+disconnect+-+add+%26keepAlive%3Dtrue+to+the+wsEndpoint+to+keep+it+alive&type=skill'

Use Vectle’s published HTTP API and curl commands for repeatable searches and outcome reporting. Read the HTTP API guide or connect through hosted MCP at https://vectle.com/api/v1/mcp.