What AI does
AI analyzes tasks, changes code, adds tests, runs checks, and investigates failures. The work continues across modules.
AI-autonomous software engineering experiment
Can AI build and maintain
a browser?
ZeroWeb tests whether AI can keep a large, long-running systems project under development. One human sets direction, makes decisions, and verifies results; AI develops autonomously, and virtually no code is written by hand. The browser core and product code are in Rust.
Experimental · Not ready for everyday browsing or production use
11,500+commitsdeveloped autonomously by AI · one human: design, decisions, verification
- Test subject
- A cross-platform browser
- Implementation
- Browser core and product code in Rust
- Validation
- Builds, tests, WPT and browser comparisons
The result is judged by working software and reproducible checks, not generated line count.
The experiment
The browser is the test case.
A browser is large enough to test more than code generation. It requires long-term architecture work, standards implementation, debugging, security boundaries, graphics, and cross-platform integration. Verification runs throughout.
How the work is constrained
Specifications, module boundaries, review rules, CI, WPT, reftests, and browser comparisons decide whether a change is acceptable.
What counts as progress
A larger repository is not the goal. Features must compile, run, and pass the checks appropriate to the behavior being changed.
Runnable code
Two entrypoints into the same project.
01
ZeroBrowser
The desktop entrypoint used to integrate and test the browser subsystems. It is not yet an everyday browser.
View browser application02
ZeroWebView
A Rust API for embedding the page pipeline in host applications. The API and compatibility surface are still evolving.
View WebView libraryImplementation scope
From request to rendered output.
The repository separates the systems that load, parse, lay out, and render a page so each part can be implemented and verified independently.
- 01NetworkResources & navigation
- 02DOM + CSSDocument & rules
- 03StyleCascade & computed values
- 04LayoutGeometry & flow
- 05RenderPaint & composite
Engineering method
AI output is checked like engineering work.
Browser code in Rust
The browser core, host layers, and product code are written in Rust. External crates provide bounded low-level capabilities.
Standards-driven
Web behavior is verified against WPT, CSSWG reftests, and browser comparisons.
Checks are required
Formatting, static analysis, unit tests, integration tests, and platform CI guard the repository.
Progress has sources
Updates link to commits and roadmap items so the experiment can be inspected rather than taken on trust.
Current status
Useful as an experiment, incomplete as a browser.
Core subsystems and runnable entrypoints exist. Real-site compatibility, complete DOM and Web APIs, and everyday browser behavior remain active work.
See the detailed roadmapFoundationDOM, CSS, style, layout, rendering, network & security basics
In progressBrowser shell, render compatibility, DOM & web API coverage
AheadWebGL / WebGPU, SVG documents, animation fidelity
Start exploring
Begin with a real window.
The repository includes both a browser application and a small WebView rendering demo. Choose the path you want to inspect first.
ZeroBrowser
Launch the desktop browser entry point.
$ cargo run --bin zero-browserWebView demo
Run the smallest rendering pipeline demo.
$ cargo run --bin webview-demoSee the README for platform prerequisites and build details.
Project journal
Progress, with sources.
A running record of what changed, what is still in motion, and where each update comes from.
Inspect the experiment
Read the code.
Check the evidence.
The repository, development history, tests, roadmap, and weekly updates are public. Contributions are expected to meet the same verification rules.