BannerBye/Agents

Agents click.Someone should refuse.

AI browsers now read the web for you. Most of them treat a cookie banner as an obstacle: dismiss it, or click whatever makes it go away.

MIT · no telemetry · Playwright, Puppeteer and MCP

When a person meets a banner, there's a choice. When an agent meets one, there usually isn't: it clears the way and the page loads with whatever the click allowed. Researchers call it invisible consent.

BannerBye's engine is available on its own, so an agent can do what a careful person would: refuse, and read the page.

One call. A refusal.

import { chromium } from 'playwright';
import { prepare, refuse } from '@bannerbye/refuse';

const context = await (await chromium.launch()).newContext();
await prepare(context);           // reject string + GPC before every page
const page = await context.newPage();
await page.goto('https://example.org');
const { outcome } = await refuse(page);   // 'refused' | 'clean' | 'unresolved'

For agents that speak MCP, add the server and use the tool refuse_cookie_banner with a URL. It opens the page in headless Chromium, refuses the banner and returns the outcome plus the visible text.

{ "mcpServers": { "bannerbye": { "command": "npx", "args": ["-y", "@bannerbye/refuse"] } } }

It never clicks accept. Private and local addresses are refused.

We're testing the AI browsers.

We give each AI browser the same task on our test page, which shows a real banner with the reject button behind "Manage settings". Then we record what it does: accept, refuse, or ignore. The results go on this page, with recordings, once every browser has had the same run.

Questions

Is an AI agent's click on Accept valid consent?

Almost certainly not. Consent has to come from the person, informed and freely given. An agent that clicks Accept to get to the content records a yes that nobody gave.

What does @bannerbye/refuse do with a consent-or-pay wall?

Nothing. If the only options are Accept and Pay, it reports unresolved and leaves the page as it is. That choice belongs to a person.

Does @bannerbye/refuse send any data to BannerBye?

No. It makes no network calls of its own, sends no telemetry and stores nothing. It's the same engine as the extension, under the MIT licence.