One Agent One Browser is live · free · last verified 17 Oct 2026 · viability monitor
One Agent One Browser
An open-source browser in Rust that renders HTML and CSS without JavaScript — built by one developer and one AI agent
Read this repo, don't browse with it. JavaScript is out of scope, so most of the modern web won't render, and the author is upfront that the result isn't good. What earns your time is the constraint set: zero third-party crates, every file under 1,000 lines, three operating systems, always compilable, and a screenshot-as-feedback loop you can copy for your own agent work.
Verdict generatedVerified 28d ago · liveness 62/100 · cite: rightaichoice.com/tools/one-agent-one-browser
- Developers learning how a browser layout and paint stack works, from a codebase small enough to read in a weekend
- Engineers studying how one coding agent performs across a multi-day, multi-platform build
- Rust developers curious what a zero-dependency GUI, layout, and text-rendering stack looks like
- Educators teaching web standards with a fully inspectable, MIT-licensed implementation
- Anyone wanting a daily-driver browser — JavaScript is out of scope for this build
- Non-technical users looking for a Chrome or Firefox alternative
- Teams needing support contracts, SLAs, or managed deployment
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip One Agent One Browser if you need to check your email, log into a dashboard, or open any site that leans on JavaScript — none of that will render here.
No pricing model is published on the project page — this is an MIT-licensed repository you clone and build yourself, and prebuilt binaries ship as public GitHub releases. There is no seat, subscription, or usage meter to compare against commercial browsers.
In short
One Agent One Browser — An open-source browser in Rust that renders HTML and CSS without JavaScript — built by one developer and one AI agent. Best for Developers learning how a browser layout and paint stack works, from a codebase small enough to read in a weekend, Engineers studying how one coding agent performs across a multi-day, multi-platform build, Rust developers curious what a zero-dependency GUI, layout, and text-rendering stack looks like. Free to use.
What is One Agent One Browser?
One Agent One Browser — An open-source browser in Rust that renders HTML and CSS without JavaScript — built by one developer and one AI agent. Best for Developers learning how a browser layout and paint stack works, from a codebase small enough to read in a weekend, Engineers studying how one coding agent performs across a multi-day, multi-platform build, Rust developers curious what a zero-dependency GUI, layout, and text-rendering stack looks like. Free to use.
One Agent One Browser is a public experiment, not a product release. In January 2026 a single developer worked with the Codex coding agent for roughly 70 hours across four calendar days to build a browser from scratch in Rust. The scope was fixed upfront: HTML and CSS only, JavaScript deliberately excluded, and no third-party Rust libraries at all — the Cargo.lock is empty, so every piece of the stack comes from what the operating system ships. The result is about 20,000 lines across 72 files, every file under 1,000 lines, and a codebase that always compiles. Prebuilt binaries go out as GitHub releases built on CI for Linux (X11), macOS, and Windows. The user-facing surface is small and literal. It scrolls, has a back button, and lets you click links in rendered pages. A --headless flag keeps tests from spawning windows while you work, and debug logging exposes render and layout behaviour. Fetch and render runs through X11 and cURL on Linux, with winhttp and wininet on Windows. The interesting engineering story is the feedback loop. Because the agent could not judge a page by eye, screenshots became the signal: pick a site, hand over a JavaScript-free screenshot, ask the agent to match it, and compare against baseline images in screenshot-based regression tests. Layout modules cover flexbox (src/layout/flex.rs), inline flow, floats, tables, and replaced elements, with CSS support spanning style building, selectors, custom properties, and media queries. The stated rendering targets were the author's own blog and Hacker News. The honest framing matters. The author calls it "not great" and says he would not even call it good. So read it as a worklog plus a readable MIT-licensed implementation of layout and paint internals — the opposite end of the spectrum from a daily-driver Chrome or Firefox replacement, and a different kind of artifact from a polished closed browser product.
Key features
- From-scratch HTML and CSS rendering engine written in Rust
- JavaScript excluded from scope by design
- Zero third-party Rust dependencies — Cargo.lock is empty
- Cross-platform builds for Linux (X11), macOS, and Windows
- Prebuilt binaries published as GitHub releases, built on CI
- --headless flag runs rendering tests without spawning windows
- Screenshot capture as the agent's feedback loop for rendering
- Screenshot-based regression and end-to-end tests against baselines
- Page scrolling, back-button navigation, and clickable links
- Fetch and render via X11 and cURL on Linux, winhttp and wininet on Windows
- Debug logging for inspecting render and layout behaviour
- About 20,000 lines of Rust across 72 files, all under 1,000 lines
- Flexbox, inline flow, floats, tables, and replaced-element layout modules
- CSS style building, selectors, custom properties, and media queries
- MIT-licensed source published for reading and reuse
Behind the verdict
The decision here isn't whether to switch browsers; it's whether to spend an afternoon inside someone else's agent workflow. We'd reach for this when you're designing a long-running coding-agent setup and want a concrete record of what held up over four days and 70 hours: a hard line on third-party dependencies, a rule that the tree always compiles, and a file-size cap that keeps every commit reviewable by a person. The screenshot loop is the part worth stealing. Since the agent couldn't click around and judge a page itself, the developer turned rendered images into the acceptance test: point the agent at a site, hand it a JavaScript-free screenshot, compare against baselines. If you're building agent-directed UI work, that's a pattern you can lift this week. Pass on it if you need a browser. JavaScript was excluded from the start, so anything that depends on it to render simply won't. There is no support contract, no SLA, no managed deployment — this is one developer's logbook under MIT, and the author says it works but isn't good. Closest comparison is reading a browser-engine textbook, except the code actually runs on Linux, macOS, and Windows and the commits are public. If you want a production JavaScript engine, look at Firefox or Chrome; if you want to understand layout and paint where every file fits on two screens, this is a rarer artifact. One caveat: don't treat it as a template for shipping software. It's a constrained experiment, which is why it's legible. Copy the rules and the feedback loop, not the feature list.
Models under the hood
as of 2026-09-09
Limitations
- The developer's own assessment is that it is not great and not even good — it works.
- JavaScript rendering is explicitly out of scope, so most modern sites will not function.
- The write-up describes a narrow feature set (scrolling, back button, link clicking, screenshots, headless flag) and names just two rendering targets: the author's blog and Hacker News.
- Compatibility across arbitrary websites is untested beyond those two.
- No security sandboxing, password management, or extension ecosystem is described.
- The seed data lists tabs, bookmarks with import/export, a JavaScript REPL console, extension support, and a sub-10 MB binary, but none of those appear on the scraped project page, so treat those claims as unverified.
- This is a four-day experiment, not a maintained product.
as of 2026-10-19
Researching One Agent One Browser? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is One Agent One Browser still active?
One Agent One Browser is live · free · last verified 17 Oct 2026 · viability monitor.
Viability score
How well maintained and how widely used is One Agent One Browser? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: November 2026
How we score →What do users say about One Agent One Browser?
What people actually say about One Agent One Browser — is it worth it?
Our community sentiment research written Jul 5, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
How we verified this
Every listed fact about One Agent One Browser — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 17 Oct 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.
Verification history
We have re-verified One Agent One Browser 10 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed description, who it suits, our verdict, summary, features, who should skip it
- — changed pricing fit, limitations, description, who should skip it, summary, our verdict, features, use cases, setup time, hidden costs
- — changed features, summary, who it suits, description, our verdict, who should skip it
- — changed SSL certificate
- — changed use cases, who it suits, description, our verdict, features, hidden costs, limitations, models, who should skip it, pricing fit, setup time, summary
- — changed description, who it suits, features, our verdict, who should skip it, summary
Showing the 6 most recent of 10 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does One Agent One Browser cost in 2026?
One Agent One Browser: Free to use. Pricing last verified 17 Oct 2026.
Where the pricing makes sense
The company stage and team size where One Agent One Browser's pricing actually pencils out — and where peers do it cheaper.
No pricing model is published on the project page — this is an MIT-licensed repository you clone and build yourself, and prebuilt binaries ship as public GitHub releases. There is no seat, subscription, or usage meter to compare against commercial browsers.
Has One Agent One Browser's pricing changed?
No plan price for One Agent One Browser has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick One Agent One Browser?
Pick One Agent One Browser if you are Developers learning how a browser layout and paint stack works, from a codebase small enough to read in a weekend, Engineers studying how one coding agent performs across a multi-day, multi-platform build, Rust developers curious what a zero-dependency GUI, layout, and text-rendering stack looks like, Educators teaching web standards with a fully inspectable, MIT-licensed implementation.
Look elsewhere if you are Anyone wanting a daily-driver browser — JavaScript is out of scope for this build, Non-technical users looking for a Chrome or Firefox alternative, Teams needing support contracts, SLAs, or managed deployment, Sites and web apps that depend on JavaScript to render.
Skip it if Skip One Agent One Browser if you need to check your email, log into a dashboard, or open any site that leans on JavaScript — none of that will render here.
GeneratedReal-world workflow fit
Concrete scenarios for the personas One Agent One Browser actually fits — and what changes day-one when you adopt it.
Clone the repo, build it with no third-party crates, and walk src/layout/flex.rs and src/layout/inline.rs alongside src/style/builder.rs to see how layout and CSS cascade actually connect.
Outcome: You finish a reading pass over a full layout and paint stack in a weekend instead of months, because every file stays under 1,000 lines.
Adopt the screenshot loop: capture a target page rendered without JavaScript, hand the image to your agent, ask it to match, and gate changes on screenshot-based regression tests against baseline images.
Outcome: Your agent gets a visual feedback signal it can act on, and you get a test suite that catches rendering regressions without a human eyeballing every change.
Study how the same source tree reaches X11/cURL on Linux, a native painter on macOS (src/platform/macos/painter.rs), and winhttp plus Direct2D on Windows, then mirror the CI setup that builds and releases for all three.
Outcome: You get a working reference for one codebase shipping to three platforms without pulling in a dependency tree.
Use cases
- Studying how an HTML/CSS layout engine — flex, inline layout, style builder — is actually structured in Rust.
- Watching a documented human-plus-agent workflow build a hard piece of software in roughly 70 hours.
- Copying the screenshot-driven regression test loop for your own agent-directed UI work.
- Using the ~20K-line, 72-file codebase as a semester-sized teaching example of browser internals.
- Running headless rendering in CI on Linux, macOS, and Windows from one source tree.
- Verifying an agent-assisted build claim yourself by cloning, compiling, and checking the commit hash.
Setup time & first value
How long it actually takes to get something useful out of One Agent One Browser — broken out by persona, not the marketing-page minute.
Rust developers: a few minutes to clone and build, since there are zero third-party crates to fetch — then a weekend to read the layout stack. Grabbing a CI-built binary for Linux, macOS, or Windows is immediate. Educators planning a course around it should budget an afternoon to map the 72 files to a syllabus.
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “One Agent One Browser”, and we withheld 6: 6 did not mention One Agent One Browser. We are showing none, because we could not prove any of them are about One Agent One Browser.
Official links
What are the best One Agent One Browser alternatives?
The closest alternatives to One Agent One Browser we list are Taste Skill, Tabby and DevoxxGenieIDEAPlugin. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| Taste Skill | Free | Free | — |
| Tabby | Freemium | Pricing not published | — |
| DevoxxGenieIDEAPlugin | Free | Free | — |
Alternatives to One Agent One Browser
View all
Taste Skill
Open-source SKILL.md rules that stop AI coding agents shipping generic frontend UI
Tabby
Open-source, self-hosted AI code completion with an in-IDE answer engine, inline chat, and the Pochi agent
DevoxxGenieIDEAPlugin
Free open-source JetBrains AI code assistant with agentic coding, spec-driven development and local LLM support
Tools that pair well with One Agent One Browser
Common stack mates teams adopt alongside One Agent One Browser, with the specific reason each pairing earns its keep.
Taste Skill
Open-source SKILL.md rules that stop AI coding agents shipping generic frontend UI
Tabby
Open-source, self-hosted AI code completion with an in-IDE answer engine, inline chat, and the Pochi agent
DevoxxGenieIDEAPlugin
Free open-source JetBrains AI code assistant with agentic coding, spec-driven development and local LLM support
One Agent One Browser vs its closest rival
One Agent One Browser's closest head-to-head is with Locus Robotics.
Our One Agent One Browser vs Locus Robotics verdict written Jul 5, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
Head-to-head comparisons
Frequently asked questions
Categories
Best-of guides
For makers of One Agent One Browser
- Get a Verified Listing for One Agent One Browser ($39): a written decision within 1 working day.
- Free listing for another tool: Free reviews are decided in order, within 3 weeks of the review starting.
Used One Agent One Browser? Help shape our editorial sentiment research.