<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Todd Schiller - Chrome</title><link href="https://toddschiller.com/" rel="alternate"></link><link href="https://toddschiller.com/feeds/tag/chrome.atom.xml" rel="self"></link><id>https://toddschiller.com/</id><updated>2026-05-26T00:00:00-04:00</updated><subtitle>Human ✘ Artificial Intelligence</subtitle><entry><title>Did Google sneak a local LLM model into Chrome?</title><link href="https://toddschiller.com/blog/chrome-local-ai-linkedin-filter.html" rel="alternate"></link><published>2026-05-26T00:00:00-04:00</published><updated>2026-05-26T00:00:00-04:00</updated><author><name>Todd Schiller</name></author><id>tag:toddschiller.com,2026-05-26:/blog/chrome-local-ai-linkedin-filter.html</id><summary type="html">A response to FUD around Chrome's new Local AI models, plus a demo using PixieBrix + Local AI to filter my LinkedIn feed.</summary><content type="html">&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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!&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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? 😆&lt;/p&gt;
&lt;!-- markdownlint-disable MD013 --&gt;
&lt;div style="position: relative; padding-bottom: 56.25%; height: 0;"&gt;
  &lt;iframe src="https://www.loom.com/embed/8a1082b28512434588447b05b32594e1?hideEmbedTopBar=true" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"&gt;&lt;/iframe&gt;
&lt;/div&gt;
&lt;!-- markdownlint-enable MD013 --&gt;
</content><category term="Browser Extensions"></category><category term="AI"></category><category term="Chrome"></category><category term="browser extensions"></category><category term="PixieBrix"></category><category term="local AI"></category></entry></feed>