LIVE · auto-refresh 60s

Everything running right now — in one place

Three jobs scrape Smyths at the same time, each for a different reason. They were on separate tabs; here they are side by side. Numbers are live — .

What's actually running

Status: Production day 1 is complete — 2,974/3,000 (99.1%); the 26 misses are pages with no product data, not captcha or block failures. After the original wedge the run was made crash-proof (short capped passes + per-pass watchdog). Day 2 is now running in the Linux worker container — the production Docker image (Tor + Xvfb + Chrome), so there's no on-screen browser to stall. The exit study (qwen3-vl-32b) and the 4-arm shootout remain a day-1 / one-shot sample.

The two 3k/day runs

Same target (3,000 URLs/day, every region, over Tor), different jobs — so some columns only one of them measures. Production is on day 2 (day 1 complete, 2,974/3,000); the exit study is a day-1 sample.

⚠ Day 2: 36 of 3,000 didn't yield a product — see the full report ›
runstatusURLs doneexits captcha ratedoodles met / solvedpages parsed OKpace
loading…

Solver shootout — 4 methods, same 500 URLs

A one-shot comparison: each method scrapes the same sample on its own Tor, in parallel. Captchas only show on the rare hostile exit, so "doodles met" is small — that's where the methods actually differ. Full breakdown ›

methodstatusURLsexits doodles met / solvedpages parsed OKpace
loading…

Where each model clicked

The same real puzzles through every candidate. Green = the correct doodle; red = where the model clicked. Overlap = hit, scattered red = miss — usually the cheaper models find the doodles but order them wrong.

Loading…