Configure a Stealth Browser
Stealth is mostly about not contradicting yourself. BCTRL runs Kameleo underneath, which picks a real, internally coherent fingerprint - your job in the config is to keep the parts you control (proxy geo, locale, WebRTC) telling the same story.
📸 Content TODO: run this once and embed the resulting pixelscan screenshot (a clean “consistent” result). A CreepJS capture works too. Date-stamp it in the caption - detection checkers evolve and readers will re-test.
Why these knobs
stealth: "ultra"- the anti-detection hardening level.medium/high/ultratrade resource use for depth; start withhighand move up if a target still challenges you.- Sticky rotating proxy - rotation between sessions, one exit IP within a session. An IP that changes mid-session is itself a signal.
fingerprintfilters, not values - BCTRL defaults to a desktop Windows search and randomly selects Chrome, Edge, or Safari whenbrowseris omitted. You can narrow Kameleo’s search further (desktop+windows+chrome), and it picks a real fingerprint where canvas, WebGL, fonts, and UA already agree. Never hand-build the parts yourself.localematches the proxy country - a US exit IP with ade-DElanguage stack is a contradiction detectors look for.webRtcProxyOnly- WebRTC is the classic side channel that reveals the real IP behind a proxy; force it through the proxy.
Keep the identity across sessions
A fingerprint that’s brand new on every visit is also a signal. For flows that return to the same site, use a profile-backed runtime (config.profile: true): cookies, logins, and the fingerprint identity persist across starts, so you come back as the same browser - not a fresh stranger.
Next
- Runtime configuration - every config option
- Proxies - pools, static IPs, and bring-your-own
- Solve CAPTCHAs - for the challenges that still get through

