x-crawl
Flexible Node.js crawler library
Runssource: GitHubhomepageTypeScriptMITcommit 0c8d0c8c51b8
TypeScript, MIT licensed. The project labels itself: ai, ai crawl, chromium, crawl, crawler, fingerprint, flexible and javascript.
x-crawl runs. An Argusic agent installed it in 17 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
x-crawl library builds successfully; its crawlData, crawlHTML, async/sync modes, baseUrl, timeout, errorCollect, proxy rotation, and Puppeteer browser APIs work correctly against a real HTTP server and CONNECT proxy.
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js 18.19.1 is below the project's requirement (>=24.16.0). vitest runner fails with 'SyntaxError: Unexpected token with' because Node 18 does not support the `with { type: 'json' }` import attribute that vite/vitest emit.8 minutes
- TypeScript build error: `CookieParam` type from devtools-protocol incompatible with puppeteer-core's `CookieParam` (partitionKey.sourceOrigin missing)3 minutes
- vitest 3.2.4 and @vitest/coverage-v8 3.2.6 version mismatch3 minutes
- TypeScript build error: `PuppeteerLaunchOptions` export renamed to `LaunchOptions` in puppeteer v241 minute
- Install time
- 17 minutes
- Cold machine to finish
- 34 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- node --input-type=module importing publish/dist/x-crawl.js with a real HTTP server on :8888 and a CONNECT-capable proxy on :7890. All 11 checks passed.
- Model tokens used
- 436,435
- Exact commit tested
- 0c8d0c8c51b8
- 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.
All 11 tests pass. Let me now compile the final report exec /bin/sh -lc 'ls -la /work/repo/publish/dist/x-crawl.js && wc -c /work/repo/publish/dist/x-crawl.js'… succeeded in 0ms: -rw-rw-r-- 1 runner runner 89441 Oct 5 10:54 /work/repo/publish/dist/x-crawl.js 89441 /work/repo/publish/dist/x-crawl.js All 11 tests pass with zero failures. Here's my final report: 2026-10-05T11:10:33.122702Z ERROR codex_core::session: failed to record rollout items: thread 01a10… 2026-10-05T11:10:33.123029Z ERROR codex_core::session: failed to record rollout items: thread 01a10… tokens used 436,435 All 11 tests pass with zero failures. Here's my final report:
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 4 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.
What did not, or is not known
- Took 17 minutes to install, slower than the median of the 89 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 90 ai projects Argusic has installed and timed, x-crawl was the 73rd fastest to reach a running state, and 63 of 90 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.
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)
aiai-crawlchromiumcrawlcrawlerfingerprintflexiblejavascriptmultifunctionnodejspuppeteerspidertypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/x-crawl)Questions
- Does x-crawl run?
- Yes. x-crawl runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test x-crawl?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0c8d0c8c51b8. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test x-crawl?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does x-crawl take to install?
- 17 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 x-crawl need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing x-crawl?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does x-crawl compare with the alternatives?
- Of the 90 ai projects Argusic has installed and timed, x-crawl was the 73rd fastest to reach a running state, and 63 of 90 reached one at all.
- Where is the evidence for x-crawl?
- 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.