Obscura is a Rust headless browser for AI agents: Reveneau

Why it mattersTeams running Playwright or Puppeteer on many pages pay for the Chrome footprint on each worker. A smaller browser that speaks the same protocol is worth a test.

A Rust headless browser called Obscura is sitting at 31,524 stars on GitHub on 9 November. Trendshift ranked the repository 10th on its daily list today. The author posts under the name h4ckf0r0day. No real name is given on the project page. The repository was created on 13 April and had its last code push on 9 November. The project is seven months old.

What the project does

Obscura is a headless browser. A program drives it to open a page, run its JavaScript, read the result and move on. The main users are AI agents that browse the web as part of a task, and web scraping scripts. Obscura runs its own JavaScript engine built on V8. It speaks the Chrome DevTools Protocol, so existing Puppeteer and Playwright clients can drive it in place of Headless Chrome.

The author's own numbers

The README lists three comparisons with Headless Chrome. Memory use of 30 MB against Chrome's 200 MB or more. Binary size of about 70 MiB against Chrome's 300 MB or more. Page load of 85 milliseconds against Chrome's 500 milliseconds or so. These are the author's own figures. The README says the full benchmark suite lives in a separate repository. The suite includes Web Platform Tests conformance and a Chrome speed comparison. The separate repository is not linked in the README text we read.

The traction, in context

The Trendshift daily list ranks repositories by how fast they are being picked up that day. It is not a measure of lifetime popularity. A 10th place on 9 November means Obscura is one of the day's ten fastest-moving projects. The lifetime figures are 31,524 stars and 2,390 forks, built up over seven months. The licence is Apache 2.0. The homepage is obscura.sh.

Where it fits in a team

A team that runs headless Chrome for scraping or agent browsing can read this as a replacement to try. It speaks the Chrome DevTools Protocol. That is the same wire protocol Puppeteer and Playwright use. The cost of a single browser process is the memory per worker times the number of workers. A smaller process means more workers per machine and a smaller cloud bill. A team that runs one browser on a laptop may see no gain at all. A team that runs hundreds per day may see a real one.

The faults to check before moving a production job. One, the speed numbers are the author's own. Two, the author is pseudonymous and the project lists no company behind it. Three, Web Platform Tests conformance is not shown in the README. Run a script that depends on less common DOM features on a test case first.

Source

GitHub, h4ckf0r0day/obscura
Trendshift, daily ranking for 9 November

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.