Mission Tabs
Native mission-aware tabs organized around operational work instead of isolated URLs.
Native Chromium Rebuild — Active Development
A native browser for IT, DevOps, cloud, and technical operations.
TAHAI Browser is being rebuilt from the Chromium source tree as a fully native desktop browser—not an Electron wrapper, WebView2 shell, CEF application, or simulated browser interface.
Development truth: the native browser is not yet available for download, production deployment, Microsoft Store submission, or GA use.
Project direction
Chromium-native architecture from the browser window down.
The new generation is based on Chromium’s native desktop architecture, including native browser windows, profiles, tabs, WebContents, storage, permissions, downloads, DevTools, session restore, and physical input handling.
The legacy Electron browser remains a reference source for approved concepts, branding, Mission Control workflows, recipes, tools, schemas, and user-facing content. It is no longer the architectural foundation.
Chromium source pin
Fixed source identity.
- Chromium version
150.0.7871.186- Chromium revision
0fcdce5f4fdec8d442d7df760cb541f1ca6e446d- Current source milestone
- NATIVE038 — Privacy and Local Data Inventory
- Next milestone
- NATIVE039 — Protocol, Extension, and Permission Governance
Primary differentiator
Mission Control, built into the browser.
TAHAI Browser is intended for operators moving across cloud consoles, identity platforms, DNS, hosting, GitHub, deployment systems, logs, documentation, runbooks, support workflows, and technical evidence.
Multi-pane layouts
Operational views with active-pane navigation and deliberate side-by-side context.
Runbook Rail
Procedures and working guidance kept adjacent to the active mission.
Mission Timeline
A reviewable sequence of mission activity and operator context.
Evidence and redaction
Capture and support workflows designed around explicit secret-exclusion rules.
Native OpsTools
Browser-native technical tools without exposing generic command execution.
Admin profiles
Profile-scoped operational contexts, policy, and governed feature services.
Mission Recipes
Reusable operational launch patterns with bounded references and workflows.
Enterprise and security work
Boundaries before release claims.
- Managed policy framework with Windows Registry and GPO scaffolding.
- Privileged-boundary auditing and remote-site isolation.
- WebUI payload validation and profile-scoped feature-service rules.
- No generic command-execution interface.
- No secret-retrieval API.
- Cookies, tokens, credentials, authorization headers, and browser-storage dumps are prohibited from evidence and support output.
Current blocker
Runtime proof still requires the pinned checkout.
The full pinned Chromium checkout is not currently available at the required development path, so the project does not claim a completed native binary, headed Windows proof, installer, MSIX, signed release, release candidate, or GA build.
Release rule: source-side progress is not presented as a finished download. Enterprise Gates G3, G4, and G5 remain open until their evidence exists.
Six passes remain
The release path from governance to final gate.
Each remaining pass closes a distinct class of release evidence. Packaging follows security, privacy, diagnostics, and provenance—not the other way around.
Protocol, Extension, and Permission Governance
Extension allow/block policy, external protocols, dangerous schemes, sensitive domains, permission governance, and audit trails.
Support Bundle and Diagnostics
Build identity, Chromium revision, OS/GPU facts, active policy truth, safe errors, crash state, Mission diagnostics, and metadata-only support output.
SBOM, Provenance, and Reproducibility
Patch hashes, GN arguments, toolchain versions, SBOM, checksums, source-to-binary manifest, and Gate G5 evidence.
Windows Installer
Install, upgrade, uninstall, shell integration, default-browser registration, profile retention, and signed-artifact lane.
Microsoft Store / MSIX
Native package identity, Store assets, capabilities, protocol associations, update smoke, and Partner Center evidence.
Legacy Migration and Release Gate
Safe optional migration, installed Windows proof, physical mouse navigation, authentication compatibility, window-state review, known issues, and final package decision.
Long-term directionModes that fit the way the user works.
Beyond Mission Control, a planned Daily Driver mode and other adaptive modes may let TAHAI Browser organize itself around a user’s normal working patterns and preferred context. This is a long-term goal for a free application—not a near-term release promise—and it will be balanced against TAHAI’s other active projects.