The decision to build Browserless was validated when founder Joel Griffith found a GitHub issue about running a specific browser technology in production. The high volume of comments and activity was a clear signal that he had stumbled upon a widespread, painful problem worth solving.

Zed founder Nathan Sobo's first IDE, Atom, used web technologies (creating Electron) for maximum extensibility. This drove rapid adoption but hit a performance wall that required a complete rewrite. Performance cannot be added later; it's baked into the initial architecture choice.

Despite a wave of new AI-powered browsers from companies like OpenAI, nearly all are built on Google's Chromium engine. This stifles deep innovation and competition at the web's foundational layer, creating a monoculture with an illusion of choice.

Instead of forking Chromium's C++ UI, the Atlas team built a native Swift UI. While this required rebuilding table-stakes features, it gives them complete control over the user experience and makes it easier to hire modern iOS/Mac developers who are scarce in the C++ UI world.

ChatKit is delivered as an embeddable iframe, not an open-source library. This is a deliberate choice modeled after Stripe Checkout, allowing OpenAI to push updates (new models, UI features, modalities) automatically. This saves developers from constant frontend maintenance and keeps the experience cutting-edge.

Creating integrations for native desktop applications can be difficult. A powerful workaround is to use the web-based version of the app, like Slack in Chrome. This allows you to build custom Chrome extensions that can read content, trigger actions, and automate workflows.

To appeal to the "layperson" rather than tech early adopters, Comet's designers made the core browser experience familiar, like Google Chrome. This reduces cognitive load, allowing users to focus their limited learning bandwidth on the novel AI features, even if it disappoints power users expecting a radical redesign.

Contrary to fears of chaos, allowing users to modify their software can create more stability. Users can craft a predictable, long-lasting environment tailored to their needs. This control protects them from disruptive, top-down redesigns pushed by a distant corporate office.

The recent explosion of so-called "AI browsers" isn't a true browser war. Most are just different user interfaces built on Google's Chromium engine. This means they aren't independent and don't contribute to the browser engine diversity that is critical for an open web.