Browser Sessions

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.

---

​

The Browsers page

Click Browsers in the left sidebar to open the Browsers page. It lists all browser sessions in your organization. Each row shows:

---

​

Creating a session

Click the Create Browser Session button at the top of the Browsers page. A panel opens with the following settings: Click Create to launch the session. It appears in the table within a few seconds.

---

​

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.

​

Recordings

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

​

Downloads

Files downloaded by the browser during the session. Click any file to save it locally.

---

​

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.

---

​

Using a session with an agent

You can also run agents inside an existing session:

1. Copy the session ID from the Browsers page
2. Go to Agents and click Run on your agent
3. On the parameters page, scroll to Run Settings
4. Paste the ID into the Browser Session ID field
5. Click Run Agent

The agent picks up where the browser left off: same page, same cookies, same form data.

---

​

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

---

​

When to use sessions vs agents

If your steps run back-to-back with no pauses between them, an agent is more efficient. Agent 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 an agent

---

​

Sessions vs profiles

---

​

What’s next