A← Index

bare

A web browser written from scratch in Rust, built to be driven by agents.

RoleSolo: design & build
TypeBrowser engine
StackRust · Wayland · MCP
StartedOctober 2026

IWhy I built it

I wanted to know how a browser works, part by part. Reading about it was not enough, so I write each part myself: networking, TLS, parsing, layout, paint and JavaScript.

I also wanted a browser that my coding agents can drive and that I fully understand. When a page fails, I can follow the failure into my own code instead of a black box.

1,390+commits since 28 Oct
16Rust crates
48public-site journeys pass
0TLS libraries

IIWhat is inside

The core parts are written by hand. Each part lives in its own crate with its own tests and benchmarks. A page goes through them in this order:

Network and TLS
DNS, TCP, HTTP/1.1 and HTTP/2. TLS 1.3 and 1.2, including the cryptography, with no TLS library.
HTML and CSS
An HTML tokenizer and tree builder. A CSS tokenizer, parser, selector matcher and style cascade.
Layout and paint
A box tree with block and inline layout. PNG, JPEG and WebP decoders. A display list painted into a Wayland window with pointer and keyboard input.
JavaScript
A parser, a heap and a tree-walking interpreter, with no JIT. Timers and fetch run, so pages that depend on scripts can load.

IIIBuilt for agents

bare-drive runs a user journey from a step file: open a page, type, click, wait, check. It sends input through the same path as a real user, so a passing journey means the page works in the window.

bare-mcp exposes the same journeys as an MCP server. A coding agent can test a web app end to end, headless or in a visible window. When bare fails on a site, the agent files an issue with the tool call, the result and the expected result. My agent project deck uses bare as its only browser.

On 10 November 2026, bare passed 48 journeys on public sites, with no failures and no skips.

IVHow I work on it

Each topic follows the same loop: implement, run large load tests, then reduce CPU time and memory. The next topic starts only after the current one passes its checks. For a bug, a failing regression test comes first.

Since 5 November 2026, bare also uses tested open-source parts where they fit, such as ICU4X for international text. Each part must pass our own load tests before it goes in.

Limits. bare is a learning project and is not safe for everyday browsing. Only Linux has a window today, and layout and JavaScript are still in progress.

VProgress baseline

On 18 November 2026, I ran one real end-to-end test in Chrome and in bare: log in to a staging web app, create a client and an agent, then delete both. All 20 runs passed.

5.1xless memory than Chrome
1.3xless CPU time
1.25xfaster journey

Chrome's V8 still runs 17% fewer instructions on this script-heavy app. That gap is the target for the next JavaScript engine work. See the full baseline, with charts and method.

SignedArjun