







Fantastic work, thanks for making this 🙏🏼 The readme has basic information about the code, but not much about the broader project, goals, funding, etc. Do you want companies to use this as a base f...
samuelmaddock/electron-browser-shell
A minimal, tabbed web browser with support for Chrome extensions—built on Electron.
AgregoreWeb/electron-extended-WebExtensions
Extend the built-in functionality of Electron Web Extensions with additional features commonly used by browsers.
Introducing Glide, an extensible, keyboard-focused web browser
A Firefox fork with a TypeScript config that lets you build anything.

Migrating from BrowserView to WebContentsView | Electron
BrowserView has been deprecated since Electron 30 and is replaced by WebContentView. Thankfully, migrating is fairly painless.

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…


How might a browser be developed?
There’s a confluence of things that have happened recently that have made me question how browsers might be developed: On January 8th 2026, Simon Willison predicted that someone will build a browser using mainly AI-assisted tools within 3 years On January 27th 2026, one human and one agent built a browser from scratch (great experiments) On the 19th February 2026, news came out that Taalas had a chip that can spit out nearly 17,000 tokens per second by baking a model onto the chip. I would like to indulge in a little bit of projection and in my case, some science fiction of my own.

Electron Spins: a special case of Chromium mods | Little Bear Labs
John's a dev who likes to build to last; most known for his work in native-compiling languages like Rust & C++. Dive deep or collaborate: why not both?
feat: service worker preload scripts for improved extensions support by samuelmaddock · Pull Request #44411 · electron/electron
Description of Change Implements RFC #8 which aims to allow Electron applications to support additional Chrome Extension APIs. Extension background service workers can be modified using preload scr...
Why build a new browser? From intuition to reality - Blog | Lightpanda
Three years ago when we started Lightpanda, we asked ourselves a seemingly simple question what would a browser look like if it were built specifically for automation?

Claude is an Electron App because we’ve lost native
Article argues that Claude is not an Electron app not because LLMs can’t do it, but because there are no advantages left for native
Beaker Browser MVP Review: 0 use cases + 4 years of engineering = 0 users
Beaker Browser is an open-source “peer-to-peer browser for Web hackers” project led by Paul Frazee and Tara Vancil. Here’s the kind of…

Do people know I’m building an alternative to Electron and Tauri? Where you write typescript for the main and browser code and it just works. Has building, packaging, code signing, and update management built in. Bundles as small as 12MB and ship updates as small as 4KB? electrobun.dev
The Electron changes here are quite interesting. It's not "add full browser extension support to Electron". Is more like "add special limbo space where extension support and things like it are possible". github.com/electron/electron/pull/44411
feat: service worker preload scripts for improved extensions support by samuelmaddock · Pull Request #44411 · electron/electron
github.com