Perplexity Comet: The AI-Native Browser Arrives

01 More than a chatbot in a sidebar

Every major browser now has an AI assistant bolted on: a sidebar you can summon to summarize the page or draft an email. The assistant is a passenger; the browser remains a rendering engine with tabs. Comet's premise inverts that relationship. The assistant is not beside the browsing — it is the organizing principle of the browsing, present in every tab, able to read what you see, answer questions grounded in the live page, and carry context forward across the session.

The distinction sounds like marketing until you use it. A sidebar assistant answers questions about the current page. An AI-native assistant can be told a goal — compare these three products, track this price, fill this form — and work across pages while you watch or while you do something else. The first is a feature. The second is a different category of software.

02 From answer engine to full surface

Perplexity's business began as a search replacement: ask a question, receive a cited synthesis instead of ten blue links. That product attacks one slice of online life — the moment of asking. But the browser is where the answers get used: purchases get made, forms get filled, articles get read, comparisons get finished. Moving to the browser gives the engine both sides of the transaction — the questions and the actions that follow them.

There is a harder business logic underneath. Search traffic is the most valuable attention on the internet, and it flows through defaults: the browser's address bar, the phone's preinstalled engine, the operating system's assistant. An answer engine without a surface lives at the mercy of those defaults. A browser — even a niche one — is a beachhead that cannot be taken away by a platform partner turned competitor.

03 How Comet works

Comet is built on Chromium, so compatibility with the existing web comes free. The differentiation is the layer above it: an assistant that maintains a session-long memory of what you have read and asked, page-local question answering with citations back to the live DOM, and agentic task execution — the assistant navigating, clicking, and filling on your behalf under your supervision. Reviews of early builds converge on the same pattern: the question answering is strong, drawing directly on Perplexity's search synthesis engine; the agentic actions are promising but uneven, occasionally mis-clicking or stalling on complex multi-step flows.

The honest engineering read is that question answering is a solved-enough problem while agentic browsing is not. Getting a model to summarize a page reliably is table stakes. Getting a model to complete a checkout flow across five pages without an error that costs the user money is a frontier problem, and everyone shipping agent products is at the same early point on that curve.

04 The competitive board

Comet enters a board that reformed quickly. OpenAI shipped its own browser; The Browser Company rebuilt Arc's successor around AI; Microsoft has pushed Copilot deep into Edge; and Google — which owns both the dominant browser and the dominant search default — is integrating its models into Chrome itself. Perplexity's distinguishing bet is that it is the only entrant whose core product was already a question-answering engine, so the browser is a natural extension rather than a defensive add-on.

05 The trust surface problem

A browser that renders pages is a passive window. A browser that acts for you is a fiduciary. The security surface expands qualitatively: the assistant reads everything on every page you visit — including pages with your bank balance, your medical portal, your email. It can click, and clicking can buy, submit, or publish. Prompt-injection attacks that are merely embarrassing in a chatbot become materially dangerous in an agent with a pointer: a malicious page can attempt to instruct the assistant as if it were the user.

Every agentic browser vendor faces the same unglamorous work — sandboxing what the agent can see, requiring confirmation for irreversible actions, rate-limiting autonomous flows — and none has fully solved it yet. Adoption of agentic browsing will be gated less by capability than by how quickly the industry builds the permission model that makes delegation safe.

06 Limits and economics

The immediate limits are practical: agentic flows break on sites that fight automation, the assistant occasionally misreads unconventional layouts, and heavy AI usage carries inference costs that a free product absorbs. The economic question is the deeper one — browsers historically monetize through search referral deals, and Perplexity's whole premise replaces search-result pages with synthesized answers. Comet will need to invent its economics rather than inherit the browser's, most plausibly through subscription tiers around agentic usage.

07 What it signals

Whatever Comet's individual fate, the direction it represents is already settled: the browser is being rebuilt as the runtime for AI agents, the way it was once rebuilt as the runtime for web applications. The tab bar was the interface of the 2010s. The assistant panel with task status and delegation permissions is shaping up as the interface of the rest of this decade. The open question is not whether this happens, but who owns the default when it does — and that is a question about distribution, not technology.