Limits

Limits keep browser runs stable, tool responses readable, and agent loops bounded. Prefer smaller observed steps over one large unbounded operation.

​

Browser lifecycle

​

Browser-code execution

For SDK and MCP browser-code execution, page is already in scope. Returning very large values can still make responses hard to use even when execution succeeds.

​

Observations and capture

Activity capture limits:

​

Agent variables

​

Agent runs

​

Quick actions

​

Browser resources and events

​

SDK retries

Default SDK retry config:

​

Practical guidance

When you approach a limit:

• Split long browser work into smaller observed steps.
• Write bulky output to files or downloads instead of returning it from browser code.
• Keep observations scoped with locators.
• Use maxChars, limit, cursor, and pagination fields instead of requesting everything.
• Move multi-step, stateful flows to managed browsers or SDK agent sessions.