browserless

The headless Chrome/Chromium driver on top of Puppeteer. Take screenshots, generate PDFs, extract text and HTML with a production-ready API.

Runssource: GitHubhomepageJavaScriptMITcommit 56b046acc55c

JavaScript, MIT licensed. The project labels itself: automation, browser, browserless, chrome, chromium, headless, html and javascript.

browserless runs. An Argusic agent installed it in 0.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 10 of 14 testable packages pass fully (330 tests) on Node v24.0.0 with Puppeteer 25.17.0 and Chromium 157.0.8103.50; the sole regression is the navigator.languages evasion returning an extra language tag due to the newer Chrome version.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96.7 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96.7 / 100
cost of the verifying run
$0.28 (measured)
recorded runs
2
last tested
stars
1,847
forks
91
open issues
7
watchers
9
size
30 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing browserless, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • sharp native optional dependency (@img/sharp-linux-x64) not installed - pnpm skipped it7 minutes
  • Node.js version mismatch: container has v18.19.1, project requires >= 241 minute
  • Screenshot pixel-diff threshold: project expects 0 diff without CI env, but rendered screenshots vary slightly across Chrome versions (1132, 2015, 1132 pixels diff)
Install time
under a minute
Cold machine to finish
26 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
pnpm --recursive run test (with CI=true) across all 14 workspace packages with tests: errors(16/16), devices(9/9), ai(47/47), screencast(10/10), function(68/68), lighthouse(20/20), screenshot(70/70), capture(45/45), browserless(55/55+2 skipped), goto(1 failed out of 265+). Only failure: navigator.languages test expects ['en-US'] but Chrome 157 returns ['en-US', 'en'].
Model tokens used
480,270
Exact commit tested
56b046acc55c
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

1. **Node.js version mismatch** - The project requires `node >= 24` but the container has Node 18. …
2. **sharp native optional dependency not installed** - The initial `pnpm install` installed via pn…
3. **CI test environment** - 3 screenshot pixel-diff tests (png, jpeg, iPhone) fail without `CI=tru…
2026-11-13T07:41:52.826403Z ERROR codex_core::session: failed to record rollout items: thread 01a1d…
2026-11-13T07:41:52.826501Z ERROR codex_core::session: failed to record rollout items: thread 01a1d…
tokens used
480,270
I've now thoroughly validated this repository. Here's the complete report:
**Errors encountered and fixed:**
1. **Node.js version mismatch** - The project requires `node >= 24` but the container has Node 18. …
2. **sharp native optional dependency not installed** - The initial `pnpm install` installed via pn…
3. **CI test environment** - 3 screenshot pixel-diff tests (png, jpeg, iPhone) fail without `CI=tru…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 0.5 minutes, faster than the median of the 38 comparable projects Argusic has measured.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 39 automation projects Argusic has installed and timed, browserless was the 9th fastest to reach a running state, and 27 of 39 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 0.5 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.28
Argusic Runner1/3Runs93.330.39

Topics (from GitHub)

automationbrowserbrowserlesschromechromiumheadlesshtmljavascriptnodejspdfpuppeteerscreenshottextweb-scraping

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/browserless.svg)](https://argusic.com/subject/browserless)

Questions

Does browserless run?
Yes. browserless runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test browserless?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 56b046acc55c. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test browserless?
The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does browserless take to install?
0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does browserless need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing browserless?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does browserless compare with the alternatives?
Of the 39 automation projects Argusic has installed and timed, browserless was the 9th fastest to reach a running state, and 27 of 39 reached one at all.
Where is the evidence for browserless?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion