Skip to main content
A browser session is a live browser instance that stays open between runs. Cookies, login state, cart contents, and page context all persist — like keeping a browser tab open. Use sessions when you need back-to-back tasks to share state, or when you want to interact with the browser yourself between automated steps.
Looking to use browser sessions from code? See the API & SDK guide instead.

​
The Browsers page

Click Browsers in the left sidebar to open the Browsers page. It lists all browser sessions in your organization. Browsers page with the sessions table showing columns for ID, open status, occupied status, started time, timeout, and CDP URL Each row shows:
ColumnWhat it shows
IDSession identifier (starts with pbs_)
OpenWhether the browser is currently running
OccupiedWhether a task or workflow is actively using the session
StartedWhen the session launched
TimeoutHow long the session stays open before auto-closing
CDP URLChrome DevTools Protocol address for direct connection

​
Creating a session

Click the Create Browser Session button at the top of the Browsers page. A panel opens with the following settings:
Create Browser Session panel showing fields for timeout, proxy location, browser type, extensions, and browser profile
SettingWhat it does
TimeoutHow long the session stays open, in minutes. Min: 5, max: 1440 (24 hours). Default: 60.
Proxy LocationRoute the browser through a residential proxy in a specific country. Default: US.
Browser TypeChrome (default, widest compatibility) or Microsoft Edge.
ExtensionsOptional add-ons: Ad Blocker (removes overlay ads that interfere with clicks) and Captcha Solver (auto-solves CAPTCHAs).
Browser ProfileLoad a saved browser profile to restore cookies and login state from a previous session.
Click Create to launch the session. It appears in the table within a few seconds.
Sessions bill while open, even when idle. Set the timeout to match your use case and close sessions when you’re done.

​
Viewing a live session

Click any session row in the table to open its detail page. The detail page has three tabs:

​
Stream

A live view of the browser. You can watch pages load and actions fire in real time. Click on Take Control to interact with the browser yourself. Use this to log in, dismiss a popup, solve a CAPTCHA. Browser session detail page with the Stream tab active, showing a live browser view and session controls

​
Recordings

Video recordings of activity in the session. Each recording captures what happened during a task or workflow that ran inside this session.

​
Downloads

Files downloaded by the browser during the session. Click any file to save it locally. Browser session download page with the preview or download links for anything downloaded during the session

​
Using a session with a task

Once you have a running session, you can run tasks inside it from the Discover page:
  1. Copy the session ID (pbs_...) from the Browsers page
  2. Go to the Discover page
  3. Click the gear icon to open Advanced Settings
  4. Paste the ID into the Browser Session ID field
  5. Write your prompt and run
The task executes inside your existing session. Cookies, login state, and page context from previous tasks are still there. Advanced settings panel on the Discover page with a pbs_ session ID entered in the Browser Session ID field

​
Using a session with a workflow

You can also run workflows inside an existing session:
  1. Copy the session ID from the Browsers page
  2. Go to Workflows and click Run on your workflow
  3. On the parameters page, scroll to Run Settings
  4. Paste the ID into the Browser Session ID field
  5. Click Run Workflow
The workflow picks up where the browser left off — same page, same cookies, same form data. Workflow run settings panel with a pbs_ session ID entered in the Browser Session ID field

​
Closing a session

From the session detail page, click Stop. A confirmation dialog appears. The browser shuts down immediately and the session moves to closed status. Stop browser session confirmation dialog with Cancel and Stop buttons Sessions also close automatically when their timeout expires, even if a task is still running. Set timeouts with enough margin for your longest expected task.
Closed sessions cannot be reopened. If you need the same login state later, create a browser profile before closing.

​
When to use sessions vs workflows

If your steps run back-to-back with no pauses between them, a workflow is more efficient. Workflow blocks share one browser instance with no inter-step startup cost. Sessions are the right choice when you need:
  • Pauses between steps — review results, get approval, or wait for external input before continuing
  • Human-in-the-loop — interact with the browser yourself between automated steps
  • Ad-hoc sequences — run different tasks one after another without pre-building a workflow

​
Sessions vs profiles

Browser SessionBrowser Profile
What it isLive browser instanceSaved snapshot of browser state
LifetimeMinutes to hoursDays to months
StateCurrent page, cookies, open connectionsCookies, localStorage, session files
BillingCharged while openNo cost when not in use
Best forBack-to-back tasks, human-in-the-loopRepeated logins, scheduled workflows
Use a session when you need a live browser right now. Use a profile when you want to save login state and reuse it later.

​
What’s next

Browser Profiles

Save login state and reuse it across sessions

Browser Sessions (API)

Create and manage sessions programmatically