One sentence and the Agent installs a browser itself: Moli, 88 days, 22k stars, most of them from the first two weeks of October

In Aug 20, a startup called Lexmount (揽岳智能) published a 18-minute long read. It opens with: "If the browser had been designed for AI Agents from day one, would it still look like Chrome today?" Their answer is Moli, a headless browser written in Rust from scratch. The repo was created in Aug 10, got only 21 stars by Sep 2,164, then gained nearly 10k in a week from Oct 4 to 11, and in Nov it was 6 22,716. Below: what it is, where the stars came from, why it took off at this moment, and why I wouldn't recommend building a head-on competitor.

A cloud browser company that found Chrome too expensive

Lexmount sold cloud browsers for Agent web automation and RL post-training, running on their own modified Chromium (called Ace). The blog says that at scale, waste becomes unavoidable: Agents mostly don't need images, fonts, or audio/video when reading pages, yet Chromium downloads them eagerly. When no one is watching a page, Chrome keeps laying out and painting anyway. These behaviors are too tightly bound to the engine to strip out cleanly.

So they rewrote it. Moli's motto is "structure first, pixels on demand": by default it only parses the DOM and styles, with no layout or rendering, and it lays out only when an Agent needs a screenshot. It uses V8 plus Servo's style engine Stylo and layout library Taffy. Their own numbers: resident memory is about 1/7 of Chrome's, and cold start is about 5 times faster.

The lead developer is ldm0 (Donough Liu, Beijing, who has written Rust libraries such as rsmpeg). One person made 2,817 commits. A single binary supports CDP, WebDriver Classic, and WebDriver BiDi, so Playwright connects directly. It's Apache-2.0 and runs on Linux, macOS, and Windows.

The first paragraph of the README's Quick Start isn't an install command. It's a sentence addressed to the Agent:

"Install the skills under github.com/lexmount/moli/tree/main/skills, follow the instructions to download and install the latest Moli binary, then use moli-webfetch to fetch example.com and show me the result."

Claude Code and Codex users can use it by copying and pasting.

How the stars grew

(Daily GitHub stars and charts; figures before 10-17 are taken from third-party pages)

After that, one or two hundred a day. Over the past 7 days +1,198, and in the first 7 days +1,426. It's slowly tapering off.

Where users come from

Most of the push came from GitHub's own charts. 10-03 hit #1 on the Trendshift daily chart, and 10-11 and 10-12 were #1 on the GitHub Rust weekly chart. The README header shows both badges. Hitting a language-specific chart like Rust is much easier than hitting the all-GitHub chart.

The charts drew out a circle of "machine-written" reposts. From 9 through October, more than twenty sites wrote about it: DeepWiki, heatdrop, implicator, ssdnodes, the French mondary.design, the Traditional Chinese repoinside, plus Juejin, CSDN, OSCHINA, Telegram channels, YouTube Shorts, and Reddit r/BestGitHubRepos. An Instagram Reel was captioned "#1 trending GitHub repo today". Most of these were likely auto-generated from the trending feed, pulled along by the momentum, and they sent people back to the repo.

README and overseas accounts in 7 languages. Chinese, Japanese, German, French, Spanish, and Korean. On X, 10-05 @Dinosn (5.2k views), the Japanese n8n author @so_ainsight (4.8k) in 10-07, and @peesamac from Thailand all reposted it. The Chinese account @0xGky had one post with 25k views, and the next day stars rose by 231 (11-02). The README also carries Discord and WeChat group QR codes.

A competitor promoted it for them. 10-19 Lightpanda published the blog post "Benchmarking AI-native headless browsers built from scratch", pitting Moli, Obscura, and Cloudflare Kitesurf against each other. Its conclusion was that it was 3.9 times faster than Moli. The result is unflattering to Moli, but it effectively put Moli in the same tier as the industry's top player.

Product Hunt's boost was small. 10-25 it took first place on Sunday, but in the following days it added only 166 to 384 stars per day.

Hacker News has basically nothing. Searching finds no posts about Moli or Lexmount; a r/rust post got 0 upvotes and the author deleted it.

Why now

The topic is hot. Agents need to browse the web at scale (crawling, evals, RL training), and carrying a 700MB Chrome around is too heavy. In 2026 8 through October, this topic kept producing news: 8-06 Cloudflare launched Kitesurf, Obscura added native rendering in September, and Lightpanda shipped 1.0 in October. Moli rode this wave in.

It owns the "best compatibility" position. Lightpanda and Obscura go minimal, using 30–40MB of memory, but in Lexbench, a benchmark Moli built with 1,071 real-world tasks, they succeed 53.3% and 44.9% of the time. Moli uses about 90MB and succeeds 81.9% of the time. The line "runs far more real websites than the rest" is repeated almost word for word in third-party articles. Note that this is self-reported: a blog (akillness.github.io) specifically questions its efficiency charts for mixing two benchmark runs. It is also slower than Lightpanda.

Behind it is a well-funded company running the full launch playbook. Lexmount raised a seed round in November 2025, with investors including Lenovo Capital. They shipped a benchmark repo, a cloud platform, README in 7 languages, a Product Hunt push, Discord, and a WeChat group, the whole stack. The open-source engine is free; the cloud sells concurrency, proxies, and CAPTCHA handling. Moli is the funnel into the cloud.

Same thing, a crowd of people building it

I found no project copying Moli directly; running in parallel are OpenHeronBrowser (also a Rust engine built from scratch), Periscope, and mimic.boo, and Reddit has several individual "write a browser from scratch in Rust" projects.

Things I still can't explain

10-04 to 10-11 it gained +10k in a week, yet I can't find a matching trigger outside: it never hit HN, and the biggest post that week on X got only 5 thousand views. Forks are only 2.8% of stars, while similar repos sit at 5% to 7.6%. The strangest part is that from 10-10 to 10-12 it gained about 1,000 stars a day, yet repos with 19 stars at the same time made the Rust daily chart while it didn't, appearing only on the weekly and monthly charts. GitHub's daily trending filters suspicious stars, which fits star farming or risk-control filtering, but this is not proof. WeChat official accounts and Chinese communities I can't see from outside may also explain the rise. The stargazer list isn't available through the API, so I couldn't check accounts one by one.

How many people know about it

Everyone in the niche knows it; almost nobody outside does. People building agent browsers have all seen it (Lightpanda publicly benchmarked against it, it was #1 on Product Hunt that day, dozens of aggregator sites wrote about it), but it never hit HN, no major tech outlet covered it, and no big account on X shared it.

If it were you

Verdict: C. Moli's launch playbook is worth learning, but building another "from-scratch browser engine for agents" isn't worth it. The space already has Lightpanda, Obscura, and Moli, each at 20–30k stars, plus Cloudflare, and Moli is backed by a lead developer with over two thousand commits and a funded company pushing it. An individual can't borrow either of those.

Who it suits: developers who understand browser automation, scraping, or agent tooling, who want to build an open-source project that can reach thousands of stars, and who can write Rust or Zig and get a test suite running.

Who it doesn't suit: an individual who wants to head-on write another browser engine for stars. Without Moli's manpower and benchmarks, it just becomes "yet another Rust browser," and Reddit already has several of those posts that got no attention.

How to do it, ranked by how worthwhile:

1. Be the neutral referee for this browser pack. Right now every project only cites its own benchmark: Lexbench says Moli wins, Lightpanda's benchmark says Lightpanda wins, and readers trust neither. Build a third-party agent browser benchmark repo: fix a set of real websites and tasks, run Moli, Lightpanda, Obscura, Kitesurf, and Chrome, publish the scripts, rerun weekly with automation, and publish a leaderboard. Each project will share the row that favors it, and the rivalry between them is your traffic.
2. Be the "one-line engine swap" at the top layer. Write an adapter for frameworks like browser-use, Stagehand, and Playwright MCP: one flag swaps the underlying Chrome for Moli or Lightpanda, and pages that break fall back to Chrome automatically. This addresses the most real user worry ("what if the lightweight browser can't load the page?"), and nobody has solved it in a unified way yet.
3. Learn its README and launch rhythm and apply them to your own project. On the first screen, put a prompt for the agent alongside a skills directory; ship the README in 5 to 7 languages; aim for a language-specific weekly chart; pick a bigger competitor and make a comparison table to force a response.

How to get users: follow Moli's path inside GitHub, not HN. On day one, put the comparison table at the very top of the README, with numbers that can be quoted in one line ("on the same 1,000 tasks, A passes 82%, B passes 53%"). During launch week, go after Trendshift and the language weekly charts, and the aggregator sites that repost automatically will find you. For benchmark projects, @-mention the tested projects too; they will likely respond.

When to move, before what: my estimate is before Q1 of 2027. Several projects just launched 1.0, are actively comparing against each other, and there's a shortage of a neutral yardstick. Once one project pulls ahead, or a major player like Cloudflare or Vercel publishes an official benchmark, this position is gone.

What would show I'm wrong: ① If Moli's or Lightpanda's stars double within two or three months and there are many production users, the topic isn't close to saturated, and building around the kernel (idea 2) deserves a bigger bet; ② if a third-party benchmark gets fewer than a thousand stars within a month, readers only trust official numbers, and idea 1 needs a different direction; ③ if it's later confirmed that most of Moli's 10k stars that week were bought or farmed, the "chart chain" part of its playbook loses value and shouldn't be copied.

Data and sources

GitHub: lexmount/moli repo page, README, commit history, release history, daily stars (10-17 to 11-06), Trendshift and the GitHub Rust weekly chart; stars of similar repos (early November). Blogs: browser.lexmount.com/blog/moli-ai-browser (08-20), lightpanda.io "Benchmarking AI-native headless browsers built from scratch" (10-19), and the critical article on akillness.github.io. Third-party pages: toolproofs.com (09-21), fervorai.dev (10-03), the OpenAtom Xuanwu community (09-16). Product Hunt "Moli by Lexmount" (10-25). X: @Dinosn, @so_ainsight, @0xGky. Funding info from Preqin. Places marked "inference" or "not proof" are inferences.