Native Chromium Rebuild — Active Development
Frequently asked questions
Clear answers without turning development into a release claim.
The native Browser is an active engineering project. These answers explain availability, architecture, security, legacy context, and long-term scope.
Core questions
What the native rebuild is—and is not.
These answers preserve the distinction between completed source-contract work, pending runtime proof, the historical Electron generation, and long-term product vision.
Is the next-generation Browser an Electron, WebView2, or CEF application?
No. The target architecture is a fully native Chromium desktop browser using native windows, profiles, tabs, WebContents, storage, permissions, downloads, DevTools, session restore, and physical input handling.
Can I download the native Browser now?
No. The pinned Chromium checkout is not currently available in the expected development path, final headed Windows runtime proof is pending, and NATIVE039 through NATIVE044 plus open release gates remain.
What happens to the Electron Browser?
It remains legacy reference source for approved concepts, branding, Mission Control workflows, recipes, tools, schemas, and user-facing content. It is not the architectural foundation of the native rebuild.
Will the Browser adapt to how a user works?
Adaptive Daily Driver behavior is a long-term goal. It is deliberately not part of the near-term NATIVE044 release promise because the native foundation, security evidence, and other active TAHAI projects take priority.
Will it store provider secrets or service credentials?
No public design claim permits generic secret retrieval, command execution, cookie export, token export, authorization-header capture, or raw browser-storage dumps. Service operations remain server-authorized.
Will it be free?
The project is being developed as a free application. That makes scope discipline important: native browsing, Mission Control, security, governance, diagnostics, provenance, packaging, and release proof come before expansive adaptive features.