Add managed proxy without CAPTCHA solver to stealth BYO patterns

[dprevoznik]

Summary

Adds a new bullet to the "Bring your own proxy or CAPTCHA solver" list on the stealth docs page covering the managed-proxy-without-CAPTCHA-solver pattern:

Managed proxy, no CAPTCHA solver — launch a non-stealth browser with a defined managed proxy via proxy_id. Full anti-detection config with a Kernel managed proxy and no CAPTCHA extension enabled.

Fills the gap between the existing BYO-proxy patterns and rounds out the combinations of managed vs. bring-your-own proxy with/without the CAPTCHA solver.

---

Note

Low Risk
Documentation-only change with no runtime or API impact.

Overview
Adds a third bullet to Bring your own proxy or CAPTCHA solver on the stealth docs page, describing managed proxy, no CAPTCHA solver: create a non-stealth browser with a Kernel managed proxy_id to keep full anti-detection while skipping the CAPTCHA extension.

This documents the combination that was missing next to the existing BYO-proxy bullets and the runtime disable_default_proxy option.

^{Reviewed by Cursor Bugbot for commit bb9a9ef. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Jul 15, 2026, 5:32 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[cursor]

Risk assessment: Very Low

This PR adds one explanatory bullet to browsers/bot-detection/stealth.mdx. It changes documentation only, with no production code, configuration, infrastructure, security boundary, or shared runtime behavior affected. The scope and blast radius are minimal.

  

_{Sent by Cursor Automation: Assign PR reviewers}