Consent autopilot: cookie banners handled
Cookie banners block automation on nearly every EU page. How the consent option clears them across roughly 17 CMP platforms, and why reject is the default.
Last updated:
The first obstacle on nearly every page
On almost every page in the EU, the first thing standing between your agent and its task is a cookie banner. A cloud browser meets them constantly: each fresh session looks like a first visit, so the banner is back even on a site you automated yesterday.
The consent autopilot takes that off your hands. It recognises roughly 17 consent-management platforms and answers the banner as part of observe, before candidates are collected — your instructions never need to mention cookies at all.
The three consent values
`consent` is an option on `observe`. It accepts one of three values.
| Name | Type | Description |
|---|---|---|
reject
|
string |
Declines non-essential cookies through the CMP's own reject path, then continues with the task.
Default: default
|
accept
|
string | Accepts the banner. Choose it deliberately when the content you need is gated behind consent — it is an explicit opt-in, never implied. |
off
|
string | Leaves banners untouched. Pick this when your own steps or workflow logic handle consent, or when the banner itself is what you are testing. |
Why reject is the default
Rejecting is the GDPR-clean baseline for automation on sites you do not control: no consent is granted on anyone's behalf unless you asked for it. accept therefore has to be explicit — Browserberg will not consent for you by default. And off exists because sometimes the banner is the point: consent flows you built yourself, or pages where your own code should make the choice.