---
title: "Browsers"
description: "Run, connect to, observe, and secure managed cloud browser sessions."
image: "https://help.agent.mq/og.svg"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.agent.mq/llms.txt
> Use this file to discover all available pages before exploring further.

# Browsers

Browsers run Chromium in the cloud and hand you a session you connect to over CDP. A session is isolated, recorded, and reachable from any Playwright, Puppeteer, Selenium, or plain CDP client, so the same automation runs on a laptop or in production without a local browser.

- **Create a browser session** — [Create a session and get a connection URL](/browsers/getting-started/create-browser-session).
- **Using a browser session** — [Connect Playwright, Puppeteer, Selenium, or a custom CDP client](/browsers/getting-started/using-browser-session).
- **Contexts** — [Reuse cookies, authentication, and application data across sessions](/browsers/core-features/contexts).
- **Session live view** — [Watch, click, and type in a running session](/browsers/observability/session-live-view).
- **Files and screenshots** — [Collect downloads, uploads, screenshots, and PDFs](/browsers/files/overview).
- **Long sessions** — [Survive disconnects with keep alive and custom timeouts](/browsers/long-sessions/overview).
- **Security** — [Restrict navigation, route egress, and trust your own certificate authority](/browsers/security/allowed-domains).
- **Browsers API** — [Session, context, download, replay, and upload endpoints](/browsers/api).

## What a session gives you

- A fresh, isolated Chromium instance per session, with its own user data directory.
- A CDP connection URL any automation library can attach to.
- Video replay, logs, live view, and downloads by default, so a failed run can be inspected after the fact.
- Optional persistence with a Context, so a login survives into the next session.
- Session-level settings for viewport, timeout, proxy egress, allowed domains, extensions, and custom metadata.

## Credentials

Every request to the Browsers API carries an application Agent key:

```bash
curl https://api.agent.mq/v1/browsers/sessions \
  -H "Authorization: Bearer $AGENTMQ_TOKEN"
```

The application the key belongs to owns the sessions, contexts, and stored files; see [Authentication](/getting-started/authentication) for how an Agent key is issued and revoked.

Source: https://help.agent.mq/browsers/index.mdx