invisible_puppeteer
invisible puppeteer: Puppeteer for Python that anti-bots cannot see, so no captchas: same API, anti-detect stealth headless Firefox, undetected fingerprint, bypass bot detection, web scraping and browser automation.
Runssource: GitHubPythonMITcommit eaca46830067
Python, MIT licensed. The project labels itself: anti bot, anti detect, anti detect browser, antidetect, antidetect browser, automation, bot detection and browser automation.
invisible_puppeteer runs. An Argusic agent installed it in 1 minute and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Editable install resolved all dependencies, default pytest suite passes (219/259), CLI version and fetch commands work, and the browser engine was downloaded and cached.
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 100 of 100 (the mean of this project's run scores).
At a glance
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.
- Install time
- 1 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pytest -q exited 0, 219 passed 1 skipped 39 deselected; invisible-puppeteer version prints engine version; fetch returns binary path
- Model tokens used
- 23,674
- Exact commit tested
- eaca46830067
- 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.
- **Tests**: `pytest -q` (default selection: unit + integration, no e2e/slow) exited 0 — **219 pass… - **CLI**: `invisible-puppeteer version` prints wrapper/core/engine versions; `fetch` returns the e… - **0 errors encountered** — no fixes needed. - No real credentials required; mocks not needed since nothing required third-party keys for the de… tokens used 23,674 All clean. Let me compile the final report. - **Install**: `uv pip install -e ".[dev]"` completed; all 23 packages resolved and installed. The … - **Tests**: `pytest -q` (default selection: unit + integration, no e2e/slow) exited 0 — **219 pass… - **CLI**: `invisible-puppeteer version` prints wrapper/core/engine versions; `fetch` returns the e… - **0 errors encountered** — no fixes needed. - No real credentials required; mocks not needed since nothing required third-party keys for the de…
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 1 minute, faster than the median of the 14 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 15 browser-automation projects Argusic has installed and timed, invisible_puppeteer was the 4th fastest to reach a running state, and 13 of 15 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 1 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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
Topics (from GitHub)
anti-botanti-detectanti-detect-browserantidetectantidetect-browserautomationbot-detectionbrowser-automationfingerprintfirefoxheadless-browserpuppeteerpyppeteerpythonscrapingstealthstealth-browserweb-automationweb-scrapingwebscraping
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/invisible-puppeteer)Questions
- Does invisible_puppeteer run?
- Yes. invisible_puppeteer runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test invisible_puppeteer?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit eaca46830067. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test invisible_puppeteer?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does invisible_puppeteer take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does invisible_puppeteer need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing invisible_puppeteer?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does invisible_puppeteer compare with the alternatives?
- Of the 15 browser-automation projects Argusic has installed and timed, invisible_puppeteer was the 4th fastest to reach a running state, and 13 of 15 reached one at all.
- Where is the evidence for invisible_puppeteer?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.