Picture a reader asking their browser to compare three news subscriptions, or to summarise a long investigation they have not opened. The browser's built-in agent visits the pages, extracts what it needs and hands back an answer, and the publisher's ad stack, consent banner and conversion funnel never meet a human. That is the practical meaning of an AI browser: a normal browser engine with a large language model driving it, so the assistant does much of the reading, navigating and clicking. The commercial problem for publishers is that the page is consumed while the attention that pays for it is absent, and the agent is hard to tell apart from a person.
What is an AI browser?
An AI browser wraps a standard rendering engine around a conversational agent that can act for the user. It answers questions about the pages in view, it can run multi-step tasks such as searching, filling in forms and comparing options, and it works inside the user's own logged-in sessions. Perplexity's Comet is the clearest dedicated example. Google has added similar behaviour to Chrome: The Register reported on 29 January 2026 that Chrome's "auto browse" lets Gemini carry out multi-step tasks, initially for Google AI Pro and AI Ultra subscribers in the US. The common design goal is to keep the user inside the assistant and reduce the number of pages they open themselves.
What happened to ChatGPT Atlas?
OpenAI launched Atlas on 21 October 2025 and shut it down on 9 August 2026. The Next Web reported on 10 July 2026 that OpenAI was folding Atlas into a desktop app combining ChatGPT, its Codex coding tool and a built-in browser that can visit sites, log into accounts and download files, alongside a separate cloud browser on OpenAI's servers where agents finish tasks remotely. Atlas only ever shipped for macOS. The lesson for publishers is not that agentic browsing is fading. A standalone browser product was retired, and the agentic capability moved into a general-purpose app and into browser extensions, which makes it harder, not easier, to name and block.
How do AI browsers differ from a Live Search Agent?
A Live Search Agent is a server-side bot that an assistant dispatches from its own infrastructure to fetch a page and feed one answer, usually without executing JavaScript. An AI browser acts on the user's device or in a cloud browser, runs a real browser engine, and can carry the user's cookies and login. The two surfaces create the same commercial gap from opposite directions. The Live Search Agent reads with no human attached. The AI browser has a human attached who never looks at the page. In both cases the monetisation that depends on human attention does not fire.
Can publishers block or paywall AI browsers?
Not reliably, and this is the most important finding for access control. The Tow Center at Columbia Journalism Review tested Atlas and Comet in October 2025 (published 30 October 2025). Both retrieved the full text of a subscriber-only MIT Technology Review article that ChatGPT and Perplexity's standard interfaces declined to summarise because the publisher had blocked their crawlers. Client-side paywalls, which load the text and hide it behind an overlay, can be read by an agent. Server-side paywalls withhold the text until login, but an agent acting for a logged-in subscriber can read it. CJR also reported that Atlas and Comet appear in site logs as ordinary Chrome sessions, so a robots.txt rule aimed at a named crawler has nothing to match. Blocking the agent could also block real readers.
What do AI browsers do to publisher traffic and analytics?
They reduce clicks and blur attribution. The Associated Press warned at Atlas's launch that AI browsers could cut referrals by keeping users inside generated summaries. When an agent reads on the user's device with a normal Chrome signature, the visit can look like a human session in your analytics, or like nothing at all if the answer is assembled elsewhere. Either way the channel is mislabelled: reading is overstated as audience in some places and invisible in others. Server logs and edge data are the more dependable record, because client-side tags only see what a script is allowed to run against.
Do any AI browsers pay publishers?
Perplexity's Comet Plus is the main precedent. Digiday reported on 26 August 2025 that revenue from Comet Plus, Pro and Max subscriptions is pooled, with 80 per cent going to publishers in Perplexity's programme, and that payouts split across three kinds of use: direct visits from people browsing with Comet, citations in answers, and content used when the assistant completes a task. Perplexity described a $42.5 million pool. The same report noted that Perplexity did not disclose payout amounts, Comet user numbers or how the three usage types are weighted, and that its head of publisher partnerships described the revenue as "not a humongous number yet". Treat it as a useful precedent for paying for agent-driven reads, not as proof of meaningful income. No equivalent scheme from Google or OpenAI has been confirmed in the sources reviewed for this article.
What should publishers do about AI browsers?
Three moves hold up. First, measure server-side, since tags and user-agent lists miss agents that present as Chrome. Second, decide per flow rather than per product: let automated reading happen where it is harmless, and require evidence of a human for things that matter such as checkout, bulk export or account changes. Prosopo, a bot-detection vendor, makes the same argument and notes that detection built around a product name has a shelf life measured in months; that is a vendor view, but it fits the Atlas outcome. Third, treat the read as the unit that needs a commercial answer. This is the layer blankspace works in: detecting AI and agent traffic at the CDN edge and placing contextual brand mentions into the response, so value is captured at the moment of retrieval rather than lost when no human lands on the page.
Frequently asked questions
What is the difference between an AI browser and a normal browser?
A normal browser renders pages for a person to read and click. An AI browser adds a built-in assistant that can read pages for the user, answer questions about them and run an agent that completes multi-step tasks. For publishers, the practical difference is that the human increasingly receives a summary or an action instead of visiting the page.
Is ChatGPT Atlas still available?
No. OpenAI shut Atlas down on 9 August 2026, less than a year after its 21 October 2025 launch, and moved its agentic browsing features into a combined desktop app. Publishers should assume the underlying behaviour continues under a different product name.
Can robots.txt stop AI browsers?
Generally not. Robots.txt relies on a crawler declaring its identity. CJR's Tow Center reported that Atlas and Comet sessions look like standard Chrome in site logs, so there is no declared agent to match. Behavioural detection at the server or CDN edge is a more realistic control.
Do AI browsers get around paywalls?
In CJR's October 2025 tests, Atlas and Comet read a subscriber-only article that the assistants' standard interfaces would not. Client-side overlay paywalls are the most exposed, and server-side paywalls can be read when the agent works inside a logged-in subscriber's session. A publisher's own testing against current products is advisable.
Do AI browsers pay publishers?
Rarely. Perplexity's Comet Plus pools subscription revenue and shares 80 per cent with publishers across visits, citations and agent actions, but it has not disclosed payout totals or weighting. Most agentic browsing still reads publisher content without compensation. Publishers can also monetise the AI response at the CDN edge, which is the approach blankspace takes.