camofox-browser
Stealth headless browser for AI agents, bypass Cloudflare, bot detection, and anti-scraping. Drop-in Puppeteer/Playwright replacement.
Runssource: GitHubhomepageJavaScriptMITcommit 389c996ae3c7
JavaScript, MIT licensed. The project labels itself: ai agent, anti bot, antidetect browser, automation, bot detection, browser automation, cloudflare bypass and headless browser.
camofox-browser runs. An Argusic agent installed it in 3.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Server starts with Camoufox browser under Xvfb, responds on port 9377, creates browser tabs that navigate to real URLs, returns accessibility snapshots with element refs, and processes click interactions correctly. All API endpoints function end-to-end.
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
- 4 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- npm test:unit exited 0 (878 passed, 2 skipped); npm run test:plugins exited 0 (45 passed); curl http://localhost:9377/health returned 200 ok with browserRunning=true; created tab via POST /tabs with actual navigation to example.com, got snapshot, clicked link via ref e1, confirmed navigation to iana.org via POST /tabs/:tabId/click
- Model tokens used
- 239,130
- Exact commit tested
- 389c996ae3c7
- 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.
Ran all test suites matching plugins/. Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that… Everything works end-to-end. Here's the summary: **Install & Launch**: `npm install` succeeded, server started on port 9377 with Camoufox browser pr… **End-to-End verification**: Created a tab navigating to example.com, took an accessibility snapsho… **Tests**: All 75 unit test suites passed (878 tests, 2 skipped) + all 7 plugin test suites passed … tokens used 239,130 Everything works end-to-end. Here's the summary: **Install & Launch**: `npm install` succeeded, server started on port 9377 with Camoufox browser pr… **End-to-End verification**: Created a tab navigating to example.com, took an accessibility snapsho… **Tests**: All 75 unit test suites passed (878 tests, 2 skipped) + all 7 plugin test suites passed …
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 3.5 minutes, faster than the median of the 15 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 16 ai-agent projects Argusic has installed and timed, camofox-browser was the 6th fastest to reach a running state, and 11 of 16 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 3.5 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)
ai-agentanti-botantidetect-browserautomationbot-detectionbrowser-automationcloudflare-bypassheadless-browserjavascriptnodejsplaywrightpuppeteerscrapingstealth-browserweb-scraping
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/camofox-browser)Questions
- Does camofox-browser run?
- Yes. camofox-browser runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test camofox-browser?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 389c996ae3c7. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test camofox-browser?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does camofox-browser take to install?
- 3.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 camofox-browser need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing camofox-browser?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does camofox-browser compare with the alternatives?
- Of the 16 ai-agent projects Argusic has installed and timed, camofox-browser was the 6th fastest to reach a running state, and 11 of 16 reached one at all.
- Where is the evidence for camofox-browser?
- 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.