#0201
Browser
Stealth on by default
You start a Hoody Browser instance. You don't pass a stealth parameter. The browser launches anyway, in stealth mode, with Patchright applied: navigator.webdriver removed, the Chrome runtime spoofed, the automation fingerprints scrubbed.
The team that used to maintain a Puppeteer-stealth fork, with the patch list and the GitHub issue subscriptions and the constant rebase against upstream, is doing something else now. The first scrape against the bot-detection-heavy site works on the first try.
If you do need a vanilla Chromium for a debugging run, you pass stealth=false. But that's the explicit case now. The path of least resistance is the path that doesn't get blocked.
The anti-detection stack used to be infrastructure. Now it's the default flag.