Keep Alive

​

Overview

​

Why Use Keep Alive?

• Reconnection workflows: Connect, disconnect, and reconnect to the same session
• Multiple connections: Different scripts or tools can connect to the same session
• Survive disconnects: Network issues won’t end your session
• Performance: Reconnecting to an existing session is more performant than creating a new one
• Session reuse: Re-run scripts against the same session without recreating it
• Billing optimization: keep alive lets you avoid minimum browser usage charges if running many short-lived sessions (under 1 minute)

​

Using Keep Alive

​

Creating a Keep Alive Session

import Browserbase from "browserbase";

const bb = new Browserbase({ apiKey: process.env.BROWSERBASE_API_KEY! });
const session = await bb.sessions.create({
  projectId: process.env.BROWSERBASE_PROJECT_ID!,
  keepAlive: true,
});

// Reconnect later using the same connect URL
console.log("Connect URL:", session.connectUrl);

from browserbase import Browserbase
import os

bb = Browserbase(api_key=os.environ["BROWSERBASE_API_KEY"])
session = bb.sessions.create(
  project_id=os.environ["BROWSERBASE_PROJECT_ID"],
  keep_alive=True
)

# Reconnect later using the same connect URL
print("Connect URL:", session.connect_url)

​

Releasing a Keep Alive Session

await bb.sessions.update(session.id, {
  status: "REQUEST_RELEASE",
  projectId: process.env.BROWSERBASE_PROJECT_ID!,
});

bb.sessions.update(
  session.id,
  status="REQUEST_RELEASE",
  project_id=os.environ["BROWSERBASE_PROJECT_ID"]
)

​

Keep Alive and Timeouts

const session = await bb.sessions.create({
  projectId: process.env.BROWSERBASE_PROJECT_ID!,
  keepAlive: true,
  timeout: 3600, // 1 hour
});