There's a lot of FUD around Chrome's new Local AI models. Jason Calacanis on the All-in Podcast got it wrong: Chrome didn't sneak in a local LLM model; it was in their official Early Preview Program for months.
The local LLM shipped in 148 is their general Prompt API powered by Gemini Nano. Smaller, task-specific models for language detection, translation, and rewriting have been available since Chrome 138 (June 2025), a long time at AI pace!
Local LLMs distributed with the browser are critical to a future where users control their browsing experience while ensuring privacy. Consumers cannot be expected to figure out how to connect their web tools and extensions to Ollama or LM Studio. And enterprises cannot be expected to deploy local LLM servers to desktops.
There are still valid concerns about model lock-in. That's because AI models ( especially small models) can behave differently for the same prompt. But, from what I've seen, the Chrome team has been, by and large, responsible in how they've rolled out the technology. For example, the public API shipped in 148 does not expose model-specific parameters.
Local LLMs enable a range of productivity/compliance use cases, especially for regulated industries handling financial and health data. But since this is LinkedIn, here's a fun one instead: using PixieBrix + Local AI to customize your LinkedIn feed and hide self-promotional, snarky, or sarcastic posts. The question is -- will anything be left on my feed? 😆