Self-healing extension manager for Ungoogled Chromium

Ungoogled Chromium delivers the performance and privacy users crave, but its lack of native extension integration creates real headaches. Without Google’s ecosystem, manually installing and tracking extensions becomes a tedious, error-prone process. One corrupted profile or accidental uninstall later, and suddenly you’re reinstalling half your toolkit. A developer has now solved this problem with a lightweight stabilizer that treats extensions like code dependencies—declarative, version-controlled, and self-healing.

The hidden cost of Ungoogled Chromium’s freedom

Running Ungoogled Chromium means opting out of Google’s telemetry and background services, which is great for privacy. But that freedom comes with trade-offs. The browser lacks seamless access to the Chrome Web Store, forcing users to rely on third-party sites like ungoogledextensions.com for manual downloads. This workaround might work for a handful of extensions, but scaling up introduces instability. User profiles frequently corrupt, critical extensions vanish overnight, or accidental removals go unnoticed for days—costing time and exposing users to unwanted ads.

Two incidents finally pushed one developer to action. First, a corrupted profile wiped out every extension. Reinstalling them meant collecting IDs, opening dozens of tabs, and installing each manually. The second strike happened during debugging: a single misclick uninstalled uBlock Origin, and it took three days to notice. At that point, the developer asked a simple question: Why can’t extensions be managed like infrastructure?

A declarative approach to browser stability

The solution is a lightweight Chrome extension called Ungoogle Extension Stabilizer. Instead of relying on fragile automation or manual processes, it introduces a declarative configuration system where users define their desired state once, and the tool enforces it continuously.

Users paste extension IDs into a text box—one per line—and the stabilizer handles the rest. Missing extensions are installed automatically via direct CRX downloads, while unused ones are removed on the next sync cycle. A configurable timer ensures consistency without manual intervention, and a self-healing mechanism restores accidentally removed extensions. For those who prefer manual control, a "Sync Now" button in the popup triggers an immediate full consistency pass.

The architecture is straightforward. The popup UI collects user input, a service worker manages installation and monitoring, and Chrome APIs handle storage, alarms, and extension operations. This separation ensures reliability while staying within the browser’s security constraints.

Feature                          How it works
Declarative list                 Paste extension IDs, one per line
Auto-install                     Missing extensions installed via CRX URLs
Auto-remove                      Unwanted extensions purged automatically
Scheduled checks                 Configurable timer (default: 30 minutes)
Self-healing                     Accidental removals trigger reinstallation
One-click sync                   Full consistency pass from the popup

Why direct CRX downloads beat Web Store automation

Early versions attempted to automate the Chrome Web Store by injecting scripts to click the "Add to Chrome" button. The approach was fragile—the store’s DOM structure changes often, shadow DOM complicates selectors, and the process felt like building on shifting sand.

The breakthrough came with CRX direct download URLs. These URLs trigger Chrome’s native installation flow without requiring DOM manipulation. The format is simple:

Navigating to this URL allows the browser to handle installation natively, eliminating brittle automation and reducing maintenance overhead. The stabilizer just needs to construct the correct URL and let Chrome do the rest.

Navigating Chrome’s user gesture requirement

A major hurdle emerged during development: Chrome’s chrome.management.uninstall() API requires a user gesture. Without it, the operation silently fails with an unhelpful error message. The solution was to move uninstall operations into the popup context, where every button click qualifies as a user gesture.

Each removal now triggers a browser confirmation dialog, ensuring the user’s click provides the necessary gesture for subsequent operations. The trade-off is a small increase in user interaction, but it’s the only way to stay within Chrome’s security model while maintaining automation.

How to try it today

Setting up the stabilizer takes minutes. Start by cloning the repository and loading the unpacked extension in Ungoogled Chromium or Chrome:

# Clone the repository
git clone 

Enable Developer Mode in chrome://extensions, then load the project folder. To find extension IDs, visit the Web Store URL for any extension. The identifier appears at the end of the URL, such as cjpalhdlnbpafiamejdnhcphjbkeiagm for uBlock Origin. Paste these IDs into the stabilizer’s popup, save the list, and the tool takes over from there.

The road ahead: features and community contributions

This is just the beginning. The developer has outlined several enhancements for future releases:

• Export and import extension profiles as JSON or shareable links
• Resolve extension IDs to human-readable names for better readability
• Port the stabilizer to Firefox, leveraging the similar browser.management API
• Support multiple profiles for different browsing contexts (work, personal, etc.)
• Introduce a CLI companion for programmatic extension list generation

The project is MIT licensed and open to contributions. Areas needing help include translations for the popup UI, cross-browser testing on forks like Brave or Vivaldi, UX improvements such as status indicators and theme support, and CI/CD pipelines for automated releases.

For those interested in contributing, the repository is available at github.com/TingyuShare/ungoogle-extension-stabilizer. Areas the developer specifically welcomes include UI translations, testing on different Chromium variants, UX polish, and automation improvements.

A step toward sustainable privacy browsing

Ungoogled Chromium’s ethos—no telemetry, no vendor lock-in—is powerful, but it shifts maintenance responsibility entirely to the user. Every extension becomes a dependency that must be managed manually. The Ungoogle Extension Stabilizer changes that equation by introducing automation that aligns with the browser’s privacy-first philosophy.

It’s not just about preventing lost extensions or accidental removals. It’s about making privacy-focused browsing sustainable in the long run. With a tool that enforces consistency and reduces manual overhead, users can finally enjoy the speed and independence of Ungoogled Chromium without trading convenience for control.