An experimental web browser written from scratch in Rust by an AI agent
Claude authored swb, an experimental Rust browser engine for Linux that renders eight target pages and passes 41,842 test262 JavaScript conformance tests.
By Dillip Chowdary • Nov 20, 2026 • Source: github.com

At a glance
- Product
- swb experimental browser
- Authoring agent
- Claude AI agent
- Implementation language
- Rust
- Operating system
- Linux on Wayland or X11
- Licensing
- MIT License with third-party notices
- Conformance status
- 41,842 test262 subset tests pass
In this post
Developer Senko Rasic released swb, an experimental web browser written from scratch in Rust where an artificial intelligence agent designs, writes, and maintains the entire codebase, according to github.com's report. Claude creates and updates the code under ground rules set by the human repository owner, who establishes project goals and reviews output. The software already displays its own GitHub page with scripting active.
This report details swb's architecture, AI authoring workflow, Linux build dependencies, interface controls, headless testing, and standards parity. Systems engineers, Rust developers, and software teams evaluating autonomous programming agents will find a concrete case study in engine development without manual human coding. It documents functioning rendering milestones alongside missing platform features like multi-tab browsing and media playback.
01AI code generation and custom engine crates
The swb project delegates all code authoring to Claude under explicit ground rules. The AI agent designs architectures, writes Rust implementations, and fixes issues across all crates. The human repository owner directs feature goals and reviews generated pull requests, ensuring no manual human code entry occurs during development.
To maintain focus, swb incorporates external libraries for HTTP networking, TLS, HTML tokenizing, image decoding, WOFF font decoding, font shaping, 2D rasterization, and windowing. In contrast, all core browser systems reside in the repository, including cascading style sheets, layout, visual painting, page loading, a custom JavaScript engine across crates/js*, DOM bindings, and the user interface.
02Linux toolchain and native compilation requirements
Developed for Linux on Wayland or X11, swb requires libfontconfig-dev, libxkbcommon-dev, libwayland-dev, and pkg-config on Debian and Ubuntu. Build-essential tools including a C compiler, make, and sh are mandatory because the build compiles jemalloc from source as the allocator under architectural decision record 0029. Commands run through just, with AI agent instructions in CLAUDE.md.
- Toolchain setup Install pinned Rust via rustup and rust-toolchain.toml.
- Repository download Clone the source tree using git clone.
- Automated build Run just run with the target website URL.
- Scripting execution Add the js flag to launch with JavaScript enabled.
- Cargo fallback Run cargo run in release mode against swb when just is absent.
Note: swb is developed and tested exclusively on Linux workstations equipped with Wayland or X11 display servers. Other desktop operating systems remain completely untested across the codebase. Compiling on unsupported environments is not covered by the project's automated test harness.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
03Browser navigation and keyboard interface shortcuts
The top window chrome includes back, forward, and reload buttons, a JavaScript toggle, and an address bar. Addresses without a protocol receive https:// automatically, while absolute paths open local files in the viewport. Users running from a shell can also supply relative file paths.
| Key | Action | | Ctrl+L | Focus the address bar | | Alt+Left, Alt+Right, mouse back and forward buttons | Back, forward | | Backspace | Back when no text field has the focus | | F5, Ctrl+R | Reload | | Escape | Stop loading | | Tab, Shift+Tab | Move the focus between links and form controls | | Enter | Follow the focused link | | Ctrl+A, Ctrl+C | Select all text, copy the selection | | Ctrl+X, Ctrl+V | Cut, paste in text fields and the address bar | | Ctrl+Shift+J | Turn JavaScript on or off | | Ctrl+Q, Ctrl+W | Quit |
JavaScript remains disabled by default when loading web destinations. Clicking the JS button or pressing Ctrl+Shift+J queues the toggle for the next navigation, while applying it to the current page requires a reload. The runtime demands an 8 MiB stack via ulimit -s, below which the button is gray and JavaScript stays off.
04Automation flags and Chromium compatibility targets
A headless mode enables testing without opening a graphical window, supporting flags to capture screenshots, full-page views, window chrome, layout dumps, JavaScript evaluation, and pipeline benchmarks. For external automation, swb can launch a WebSocket server on port 9222 or an ephemeral port on 127.0.0.1.
Rendering currently matches Chromium across eight target pages: senko.net, Hacker News, Wikipedia, Craigslist, Ars Technica, BBC, the swb repository, and OpenStreetMap. All except senko.net function with JavaScript enabled, and 41,842 test262 tests pass. However, worker scripts, multi-tab browsing, window.open, media playback, WebGL, and CSS anchor positioning remain unimplemented.
05Multi-license compliance and third-party standards code
The primary swb codebase is distributed under the MIT License, though several integrated components retain distinct third-party licenses. Domain handling uses the Public Suffix List under Mozilla Public License 2.0 as an approved exception under ADR 0014. Default document presentation relies on stylesheets adapted from the WHATWG HTML Standard under Creative Commons Attribution 4.0.
Rendering components derived from Chromium and Skia use the BSD-3-Clause license, requiring license notices in distributions. The repository also incorporates a Servo file under MPL-2.0, WebIDL files under BSD-3-Clause and W3C licenses, and Unicode tables under Unicode License v3. Testing fixtures for pages and fonts use separate licenses, while JavaScript fixtures remain local.
Frequently asked questions
Who writes the code for swb?
An artificial intelligence agent named Claude designs, writes, and maintains all source code, while the human project owner sets goals and reviews results.
What operating systems are supported by swb?
The browser is developed and tested exclusively on Linux using Wayland or X11, leaving other operating system platforms untested.
What stack memory does JavaScript require in swb?
JavaScript execution requires a system stack limit of at least 8 MiB configured via ulimit -s, below which the engine stays disabled.
Which web features remain unimplemented in swb?
Current omissions include running scripts inside web workers, tabbed browsing, window.open calls, media playback, WebGL graphics, and CSS anchor positioning.
Sources
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Advertisement