GalileoBrowser
GitHub

Roadmap / started 26 Jul 2026

A browser moves through gates.

Since the first standalone import, the code has expanded across the browser shell, web compatibility, security boundaries, extensions, Android, and qualification tooling. The next public goal is still a usable pre-alpha — but the code is now much further ahead than the old snapshot showed.

GalileoEngine symbol

Current source / reviewed through 30 Aug 2026

Useful progress. Clear open gates.

The source review is current through 30 August. Older dates below identify the last comparable test runs—not the current age of the project. Only a repeated, retained qualification can turn newer implementation work into a new measured result.

01

Compatibility

Bounded core shard

retained result
Last comparable run · 13 Aug286 / 286 selected subtests

Three named WPT files passed in this fixed, narrow shard. The date belongs to the measurement baseline, not to the current source state.

Source progress through 30 AugThe implementation moved beyond this shard

Web APIs, media and MSE, WebCodecs, networking, extensions, security boundaries, Android, and DevTools changed after the run. Those changes still need a fresh test over the same denominator.

Next proofBroader reproducible coverage

Repeat the fixed shard, then expand the retained WPT and real-site journeys without changing the measurement contract.

Measured 13 Aug · source reviewed 30 Aug 2026Inspect retained evidence
02

Product scope

Feature inventory

reviewed, not promoted
Last reviewed state54 / 68 observed partial

The 18 Aug catalogue records behaviour seen in 54 areas. “Observed partial” does not mean a focused qualification passed.

Progress after the snapshot67 / 68 declared scopes touched

Between 2fe12e0e8f82 and 99af1539f340, changed files intersected the declared implementation paths of 67 rows. No formal state was promoted.

Next proofReview the catalogue again

Promote individual rows only when focused evidence is retained. Broad or overlapping paths cannot prove feature completion by themselves.

Reviewed 18 Aug → 30 Aug 2026Inspect the review record
03

Security

Security qualification

qualification open
State on 18 AugIsolation not measured

Security hardening was active, but the browser did not have a retained process-isolation result or a complete product threat model.

Progress after the snapshotSecurity boundaries became concrete

A network-boundary baseline now names 10 focused Rust checks and pins 17 WPT files. Later work added fail-closed request bounds, cookie partitioning, origin-and-mode permissions, private extension contexts, and host-permission scoping.

Next proofRun and retain the qualification

The focused checks and fixed WPT selection still need a reproducible candidate run. Process isolation, signing, update security, and the full threat model remain release gates.

Source review through 99af1539f340Inspect the reviewed boundary
04

Performance

Performance baseline

benchmark open
State on 18 AugNo published baseline

Startup, page-load, memory, and long-session behaviour had not been captured under a reproducible measurement contract.

Progress after the snapshotFive implementation paths improved

Large-page responsiveness, ordinary-task batching, incremental streamed text, native-input priority, and extension-network deadlines changed in code.

Next proofMeasure the same scenarios repeatedly

Publish startup, load, memory, responsiveness, and soak results with the build, hardware, workload, and raw output recorded.

Source review through 30 Aug 2026Inspect the implementation record

Evidence index: Galileo source audit, retained W33 snapshot, and the linked records above.

Galileo evolution / 26 Jul → 30 Aug

One month. Seven verified checkpoints.

The line follows selected points that can be traced to retained results or reviewed source. It reaches the current reviewed head instead of ending at the older WPT measurement.

Galileo only7 evidence checkpoints

Swipe horizontally to inspect the complete line graph.

Loading the verified Galileo timeline…

Verified or reviewed checkpointCurrent reviewed source
Chronology not a completion score
Evidence shown in the Galileo project evolution graph
DateCheckpointEvidence
Loading the verified checkpoint record…

This graph covers selected, evidence-backed milestones through the reviewed source head on 30 August. It is a chronology, not a percentage of browser completion: a source checkpoint proves that code exists at that revision, while a retained test proves only its stated scope. The 13 August WPT result therefore keeps its real date inside the timeline and in the compatibility ledger above. Inspect the complete checkpoint data.

Repository checkpoint / reviewed 31 Aug 2026

The code moved. The gates remain.

This newer review reads the source at 99af1539f340, not only the README. These counts describe activity and test definitions; they do not replace the measured snapshot above.

Main historysource count
5,099
commits after import26 Jul → 30 Aug

A direct count from the first standalone import to the reviewed head. It measures movement, not correctness.

Browser shell testsdefined in Rust
1,021
test functions26 source files

Tests sit beside the shell, stores, runtime, protocol bridge, and desktop UI. This is an inventory, not a pass count.

Galileo harnesssource inventory
3,598
Python test functions82 extension manifests

The project has its own compatibility, evidence, extension, and release tooling rather than relying only on inherited checks.

Release qualificationopen
receipt + smoke tooling existsno current hosted pass

The latest hosted jobs ended before running their steps, so they provide no fresh passing signal for the reviewed head.

Repository checkpoint 99af1539f340; counts reproduced from git history and the source tree on 31 Aug. Full interpretation is recorded in the Galileo audit ↗.

Beyond the README

The architecture is already much larger.

These are source-level observations at the reviewed checkpoint. They show where the project has grown without pretending every path is qualified.

01 / product state

The shell owns durable browser data.

Profiles, history, bookmarks, settings, favicons, and content blocking now have dedicated Rust stores. Tabs, windows, private state, recovery, downloads, and permissions are connected at different levels in the shell.

02 / extension runtime

Extensions are a subsystem, not a placeholder.

Archive, store, and runtime paths exist, with separate modules for actions, messaging, ports, storage, and tabs. Reviewed Manifest V2 packages and the uBlock Origin compatibility gate exercise real browser-owned code.

03 / engine + tools

The work reaches below the browser chrome.

Changes extend into script and Web APIs, constellation sandboxing, DevTools storage and network actors, Android product surfaces, and reproducible pre-alpha receipt and smoke tooling.

The status boundary

Code exists. Qualification still has to catch up.

The project is no longer a thin shell. Browser state, extensions, media, developer tooling, security boundaries, Android work, and release tooling all have substantial implementation behind them.

That still does not prove hostile-page isolation, broad website compatibility, production performance, safe updates, or cross-platform release quality. The latest hosted jobs produced no step-level evidence, so this page does not call the current head qualified.

There is no public Galileo Browser release yet, and the current build is not recommended for everyday or security-sensitive browsing.

The road / fork → release

From the fork to the first release.

Completed means a bounded milestone has retained evidence. Current means the code exists and is still being integrated or qualified. Future rows stay open until their entry conditions are met.

  1. 01

    The fork

    26 July 2026. Commit 525533a36279 is the initial standalone import. It starts Galileo's own repository history from the browser work derived from Servo.

    Verified lineage: A full-history review records 93d8f85503e0 from 24 July as the earlier source base. The current hosted repository begins with the standalone import, so the evidence record preserves that provenance separately.

    Progress since the import: At the reviewed head 99af1539f340 on 30 August, 5,099 commits follow the import. That is a source-history count, not a quality score; the measured and qualified results are recorded elsewhere on this page. Inspect the lineage record.

    done · 26 Jul
  2. 02

    Cloudflare Turnstile

    1 August 2026. The official dummy-key canary completed Cloudflare's always-pass, always-fail, and forced-interactive modes: 3/3 headless and 3/3 headed, with the documented callbacks, failure code, and dummy token.

    Retained revalidation: The three controlled modes passed again on 4 August and on the rebuilt medium profile on 6 August. The 6 August checkpoint also retained 127/127 expected results in the selected Galileo regression suite. These are bounded fixtures, not a claim that every production challenge will clear.

    Source progress through 30 August: A local cross-origin click-delivery probe was added on 9 August to distinguish normal input delivery from label-to-control forwarding without contacting Cloudflare. The 14 August integration then expanded the parity probe with WebRTC and offline-audio diagnostics. This improves investigation depth; it is not a newer production clearance result.

    Open boundary: The reviewed production capture reached Cloudflare's remote /pat risk decision and received HTTP 401. Galileo does not replay challenge material, synthesize tokens, or spoof browser fingerprints; production acceptance remains Cloudflare's decision.

    last run · 06 Aug
  3. 03

    YouTube, working

    Last comparable runs · 14 August 2026. A clean-profile, no-WebDriver journey opened YouTube, searched, entered a real non-ad result, selected HD720, and completed 5/5 seeks. The retained run recorded 94.14 seconds of media progress, 65.25 seconds buffered ahead, and no page, media, or browser-panic errors.

    Second retained run: After the unattended harness was hardened, a fresh profile completed another home-to-watch journey and 3/3 seeks, with 119.75 media seconds, 67.8 seconds buffered ahead, and no page, media, or panic errors.

    The probe also found a real limit: Replaying three exact-build reports showed no clock stalls in runs one and three, but isolated a 4.056-second freeze in run two while the video was ready, unpaused, and buffered. The milestone proves bounded playback; it does not claim stall-free YouTube compatibility.

    Source progress through 30 August: The playback path gained stricter MSE initialization and mutation ordering, seek and replay liveness work, bounded append memory, safer GStreamer setup and teardown, and real pitch preservation through preservesPitch. Adjacent media work added Android Media Session handling and verified slices of raw VideoFrame, WebCodecs copy and transfer, and encoded chunk contracts.

    Current boundary: At the 30 August source review, those later changes clearly expanded the media foundation, but no newer comparable sustained YouTube run was retained. The 14 August evidence is a controlled test result, not the date when development stopped.

    last run · 14 Aug
  4. 04

    Baseline and product shell

    Implementation now spans Web APIs, networking, media, DevTools, and dedicated profile, history, bookmark, settings, favicon, and content-blocking stores. Android also has browser-specific history, bookmarks, downloads, modes, themes, and permission work.

    Progress since then: Extension archive and runtime paths became dedicated subsystems, Android gained media-session work, and deeper shell paths now carry more of the browser's durable state and product behaviour.

    now · expanded
  5. 05

    Security foundation

    Sandbox process work, origin and cookie boundaries, permission checks, private partitions, and fail-closed validation are active in code. A complete threat model, process-isolation qualification, signing, and update security remain release gates.

    Progress since then: Cookie partition and expiry evidence, origin-and-mode Android permissions, private extension-resource contexts, host-permission scope, and additional fail-closed protocol and network bounds now make those areas more concrete. The open release gates remain open.

    now · open gate
  6. 06

    Extensions and ecosystem

    The Manifest V2 runtime, reviewed packages, permissions, content scripts, storage, messaging, tabs, ports, and network interception are real code paths. uBlock Origin 1.73.0 passed a bounded package gate; full compatibility is not claimed.

    Progress since then: The runtime, store, and archive paths expanded; actions, context, messaging, ports, storage, and tabs were split into dedicated modules; receiver-liveness, failure handling, content DOM helpers, download-danger lifecycle, and hot-path performance were strengthened.

    now · qualified slices
  7. 07

    Engineering pre-alpha package

    Linux archive tooling, source-bound release receipts, artifact validation, and live/offline smoke tooling exist. The package remains unsigned and the latest hosted qualification produced no step-level evidence.

    Progress since then: The release path now also checks licences and credentials and binds its receipts more tightly to the source revision. Those safeguards improve the engineering package; they do not turn it into a public release.

    tooling · needs run
  8. 08

    Public pre-alpha

    The first public build comes after selected compatibility journeys, isolation, packaging, signing, update, accessibility, and recovery gates can be reproduced on the supported target.

    next · gates open
  9. 09

    Alpha and release qualification

    Broader Web Platform Tests, real-site journeys, accessibility, cross-platform packaging, performance budgets, crash recovery, security review, and signed updates must become repeatable rather than occasional evidence.

    future
  10. 10

    Release

    Version 1.0 begins only when the release contract is satisfied and the browser can be maintained safely after launch.

    future