Agent-first browser

A browser whose only user is software. It renders, runs scripts and returns page state to a program — and ships none of the things a browser has because a person is looking at it: no tabs, no chrome, no extensions, no window. Named here from kitesurf, the spoke’s first instance.

Not a point on the assistant↔agent axis

This spoke’s central axis measures how much the AI does unattended inside a browser someone still opens: gemini-in-chrome gates before acting, openai-atlas and perplexity-comet act and then ask. Both poles assume a human at the front.

An agent-first browser removes that assumption. The product is not a browsing experience with an assistant in it; it is page rendering as an API call. The distinction matters for how these things get judged — a consumer AI browser is judged on trust, interface and what it does with your session, and an agent-first browser is judged on cost per page, throughput, and whether the DOM it returns is the one a model can reason over.

What the design optimises instead

• Tokens. The output is fed into a context window, so what the browser returns and how compactly it says it is a cost the buyer feels per call.
• Startup, not uptime. Sessions are per-request rather than long-lived, which is the opposite of what a human-facing engine is tuned for and where kitesurf‘s claimed 3–7× CPU/memory advantage over Chromium comes from.
• Scale-out over features. Rendering the whole web matters less than rendering the pages agents are pointed at, cheaply, many at a time.

The open problems come with it

Nothing about removing the human removes prompt injection — a page that instructs the agent reading it is the same attack whether or not a person is watching, and with no user in the loop there is also no one to notice. The spoke’s standing finding applies unchanged: locality and engine choice answer cost, not safety (chrome-built-in-ai-dos-donts).

Second, an engine that serves agents well is not thereby a browser anyone could use. Conformance claims in this category tend to be pass counts on the pages that matter to the vendor, which is a different bar from the standards independence ladybird is chasing.

Related

kitesurf · ai-browser · cloudflare · browser-as-trust-intermediary · chrome-built-in-ai-dos-donts · ladybird · synthesis