I built an AI "web harness" running on a sandboxed Chromium (using a custom side-loaded plugin that talks over websockets to a "driver") to basically do anything a normal user could do in a browser. It totally bypasses any and all bot measures and only gets the ones you yourself would get as well (and passes those successfully, e.g. Cloudflare checkbox or those annoying OCR puzzles).
Not sure if I should release it, but I'm sure more people are catching onto the power of agentic browsing.
It is, because `--remote-debugging-port` is detected via the root DOM object (and that can't be changed unless you want to recompile Chromium), so for example, if you try doing a Google search with debugging enabled, you'll get blocked (usually just by being served a blank page).
`navigator.webdriver` afaik, but I think there's a couple more, I did some research on it a few months ago. If using Playwright/Puppeteer, they also have a few special things injected that you have to strip.
I built the POC by hand (just had like 3 things it could do: scroll, click, type), and then Codex used my established patterns to make it slightly more general and cleaned it up.
dvt · · focus · HN ↗
Not sure if I should release it, but I'm sure more people are catching onto the power of agentic browsing.
onion2k · · focus · HN ↗
Is that necessary? You could start Chromium with an open debug port and use Chrome Devtools Protocol to send commands.
dvt · · focus · HN ↗
LunaSea · · focus · HN ↗
dvt · · focus · HN ↗
Cakez0r · · focus · HN ↗
dvt · · focus · HN ↗