rebrowser-patches
Collection of patches for puppeteer and playwright to avoid automation detection and leaks. Helps to avoid Cloudflare and DataDome CAPTCHA pages. Easy to patch/unpatch, can be enabled/disabled on demand.
Runssource: GitHubJavaScriptMITcommit b5cb2266ec06
JavaScript, MIT licensed. The project labels itself: automation, bot, bot detection, chrome, chromedriver, cloudflare, crawler and crawling.
rebrowser-patches runs. An Argusic agent installed it in 8 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
rebrowser-patches repo installs, builds 6 drop-in tarballs, and passes all 43 test gates (detection, scenarios, smoke) with patched Puppeteer-core 25.14.0 and Playwright-core 1.64.1 defeating Runtime.Enable detection.
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 60 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18.19.1 below required >= 221 minute
- unzip binary missing, @puppeteer/browsers extraction failed1 minute
- Incomplete chrome install from prior failed attempt blocked reinstall0.5 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- node tests/run.mjs --pptr-core ... --pptr ... --pw-core ... --pw ... --chrome /tmp/chrome-test/chrome/linux-155.0.8059.84/chrome-linux64/chrome --out /home/runner/.cache/rebrowser-patches/tests-results --suites detection,scenarios,smoke exited 0 with 43/43 gates passed, final verdict PASS
- Model tokens used
- 285,186
- Exact commit tested
- b5cb2266ec06
- 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.
tokens used 285,186 Here's the final summary of what was accomplished. **What happened:** - Installed dependencies (`npm install` added 16 packages) - Built all 6 tarballs via `release/build-packages.mjs` (puppeteer-core, puppeteer, playwright-core… - Ran the full test suite (detection, scenarios, smoke) against real Chrome 155.0.8059.84 **Errors encountered and fixed:** 1. Node.js was v18.19.1, project requires >= 22 — downloaded and extracted Node v22.23.3 linux-x64 … 2. `unzip` not installed, causing Chrome extraction failure in `@puppeteer/browsers` — installed `y… 3. Incomplete Chrome installation from a prior failed attempt — cleared the stale directory with No… **Test results:** 43/43 gates passed across 3 suites (detection 12/12, scenarios 6/6, smoke 25/25).…
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.
- 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.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 22 comparable projects Argusic has measured.
Of the 23 automation projects Argusic has installed and timed, rebrowser-patches was the 16th fastest to reach a running state, and 15 of 23 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 8 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.03 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.01 |
Topics (from GitHub)
automationbotbot-detectionchromechromedrivercloudflarecrawlercrawlingdatadomeheadlessheadless-chromeplaywrightpuppeteerpuppeteer-extrarebrowserscrapingseleniumstealthweb-scrapingwebdriver
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/rebrowser-patches)Questions
- Does rebrowser-patches run?
- Yes. rebrowser-patches runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test rebrowser-patches?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b5cb2266ec06. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test rebrowser-patches?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does rebrowser-patches take to install?
- 8 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 rebrowser-patches need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing rebrowser-patches?
- 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 rebrowser-patches compare with the alternatives?
- Of the 23 automation projects Argusic has installed and timed, rebrowser-patches was the 16th fastest to reach a running state, and 15 of 23 reached one at all.
- Where is the evidence for rebrowser-patches?
- 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.