elements

As much as I struggle with on-device processing and the quality of its output compared to server models, I am excited by some of the APIs that are being built into browsers that are backed by LLMs and other AI inference models. For example, the prompt API, along with a multi-modal version that can take any arbitrary combination of text, image, and audio and run prompts against them. These APIs are neat but not yet web-exposed and many developers struggle to know what to do with a generic prompt. It’s not a solution that is natural to many people yet.

Forget the Fate of Chrome, Focus on the Fate of the Browser

In debating what undoubtedly won't happen, we're looking past some key things that are -- and might...

Google’s nightmare “Web Integrity API” wants a DRM gatekeeper for the web

It's just a "proposal," but it's also being prototyped inside Chrome right now.

Google’s Prompt API

No web standard should require you to agree to an advertising company’s “terms of use.”

Chrome silently installs a 4 GB local LLM on your computer

You did remember to opt out of AI, didn't you?

Announcing Supporters of Chromium-based Browsers

Since Google announced the Chromium project in 2008, we have been excited to build on the great foundations of open-source web browsers and contribute to the continued d…

WebMCP  |  AI on Chrome  |  Chrome for Developers

WebMCP has two APIs that allow browser agents to take action on behalf of the user.

Open Responses

This is the standardization effort I've most wanted in the world of LLMs: a vendor-neutral specification for the JSON API that clients can use to talk to hosted LLMs. Open …

Origin Trials

Chrome origin trials allow developers to safely experiment with web platform features

What Comes After Chrome

I co-created the world's most popular browser. Now, I'm joining The Browser Co to fulfill an old dream.

Web Install API Dev Spec

Web Install API Dev Design Spec Author: Amanda Baker, Diego Gonzalez, Kristin Lee, Lia Hiscock Spec status: Last updated: Links: Explainer | Chrome Status | CR bug | UX changes review doc Feature Overview Introduction Goals Non-goals Concepts Interfaces and Interactions JS API changes navig...

A Chrome-killing browser will be OpenAI's next big shot at Google, according to a new report

Is BrowserGPT in the cards? It’s a long way off, if it is…

Sawyer Hood on Twitter / X

Introducing the new dev-browser cli. The fastest way for an agent to use a browser is to let it write code. Just `npm i -g dev-browser` and tell your agent to "use dev-browser" pic.twitter.com/U8VmsT5XVc— Sawyer Hood (@sawyerhood) March 25, 2026

jack (@jack@mastodon.sdf.org)

#Mozilla wants to know what you want from them and, in particular, #Firefox. Let. Them. Know. https://mozillafoundation.tfaforms.net/201

Stop Ignoring the Browser: The Biggest Frontend Shift in a Decade

Native browser APIs now provide powerful alternatives for routing, state management, and components. Never mind the frameworks, use the browser.