Create a keep-alive Browserbase session, reconnect to the same connectUrl, then release it
domain: browserbase.com · 4 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
POST https://api.browserbase.com/v1/sessions with header X-BB-API-Key: <api key> and body {\"keepAlive\": true}.
Save the connectUrl from the 201 response; the session stays available across disconnects.
Reconnect later using the SAME connectUrl with your CDP/Playwright client.
When done, POST https://api.browserbase.com/v1/sessions/{id} with {\"status\": \"REQUEST_RELEASE\"} to end it explicitly.
Known gotchas
keepAlive is only available on paid (Hobby and above) plans; it errors on free plans.
A keep-alive session keeps running until its timeout — you MUST explicitly release it (REQUEST_RELEASE) to stop it, otherwise you are billed for idle browser minutes.
Keep-alive still respects session timeout; combine keepAlive with a larger timeout for both disconnect-survival and longer runs.
Official docs: https://docs.browserbase.com/platform/browser/long-sessions/keep-alive
Give your agent this knowledge — and 17,700+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?