antibrow/antibrow
Kernel-level antidetect browser with the Playwright API you already write. Python + Node SDKs, MCP-ready, unlimited local profiles. Linux x64 + arm64, macOS Intel + Apple Silicon, Windows x64.
What it solves
AntiBrow provides a way for AI agents and automation scripts to browse the web without being detected as bots. It solves the problem of "browser fingerprinting," where websites use technical markers (like GPU, audio, and font settings) to identify and block automated traffic, especially those using standard tools like Playwright.
How it works
Instead of using JavaScript to fake browser settings, AntiBrow modifies the browser's C++ layer (the engine level). It uses coherent fingerprints sampled from real devices, ensuring that all technical markers agree with each other. It integrates directly with the standard Playwright API, allowing users to drive the browser using familiar tools. It also includes an encrypted relay protocol to hide proxy signatures and a "Recipes" system for task-specific site adapters that return structured data instead of raw browser handles.
Who it’s for
It is designed for developers building AI agents, web scrapers, and automation engineers who need to bypass advanced bot detection systems (like Cloudflare or DataDome) while maintaining persistent, portable identities.
Highlights
- Engine-level spoofing: Fingerprints are handled in the C++ layer to avoid detection via JavaScript prototypes or stack traces.
- Coherent profiles: Uses real-device data across 30+ categories and 500+ parameters to prevent contradictory fingerprints.
- Android emulation: Allows desktop machines to appear as real Android devices with mobile client hints and touch input.
- Encrypted relay: A custom
relay://transport that uses AES-256-GCM to hide proxy-protocol signatures. - Standard Playwright API: Works with existing Playwright scripts by changing only the launch method.
- MCP server mode: Enables AI agents to drive browser profiles directly.
- Portable identities: Cookies, storage, and passkeys are saved in
.fpprofilefiles that can be exported or synced.
Related
- Project
- Project
- Project
- Project