Writing

Every way to install a Chrome extension is closed except one

CCalyndraeEngineering notes, Hub

The Hub was meant to write extensions into a Chrome profile while Chrome was closed, but an afternoon of measuring showed that route, along with three others, is shut.

The assumption

The first design was a three-step wizard, where you'd close every Chrome window, choose your profiles and then install. Underneath all that, though, it quietly assumed the Hub could register an extension while Chrome wasn't looking.

What Chrome actually does

Registering a packed extension the per-user way, under HKCU with no administrator, does actually install it, since Chrome unpacks it into the profile and writes a settings entry. Then it turns around and disables it with reason 256, DISABLE_NOT_VERIFIED, because there's no Web Store signature.

"active_bit": false,
"disable_reasons": [256],
"from_webstore": false,
"location": 3

There isn't even a pending prompt you could accept. Installed but permanently disabled is honestly worse than being refused, because a wizard built on it would look like it succeeded every time while delivering nothing.

The other three routes

RouteResult
Self-hosted update URLRejected: Chrome wants a Web Store proof on the package wherever it came from
Developer mode, unpackedChrome 149 disables sideloaded and unpacked extensions after an update
Enterprise policyNeeds an administrator and a managed device
--load-extensionParsed and ignored on Chrome 152; removed from branded builds in 137

The last row was written down in my own notes as working, which was true of the design but hadn't been true of the binary for fifteen versions. Measuring what you already believe is how you find that kind of thing.

The one that works

What does work is Extensions.loadUnpacked, sent over --remote-debugging-pipe to a Chrome the Hub launched itself. The method is pipe-only, which is fine, because the alternative, a debugging port, would open a listener that any local process could drive.

The cost is real, though. Extensions run in the browser the Hub opens rather than the Chrome you already have, since Chrome 136+ refuses the pipe on the default profile, where an attached client could read cookies and saved passwords. They also don't survive a restart, so the Hub opens that browser each time and closes it again when it quits.

What was not done

Publishing to the Web Store would work, but it would move the paywall into a runtime check inside the extension, which is the weakest place for it. So instead, the packages stay private and leave through the same signed, single-use, entitlement-checked download as the apps. The wizard is gone, and what replaced it is a list of what your plan covers plus one button.

This is a shorter version of a post on the Pioneering blog, so if you want the full story, read the original on pioneering.app.

Next postThe plan that costs the most could download the least