From bb9a9ef73a73841723d4678cfd1daebeca7f991b Mon Sep 17 00:00:00 2001
From: dprevoznik <58714078+dprevoznik@users.noreply.github.com>
Date: Wed, 15 Jul 2026 17:31:45 +0000
Subject: [PATCH] Add managed proxy without CAPTCHA solver to stealth BYO
 patterns

---
 browsers/bot-detection/stealth.mdx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/browsers/bot-detection/stealth.mdx b/browsers/bot-detection/stealth.mdx
index e21d0f27..673d3de0 100644
--- a/browsers/bot-detection/stealth.mdx
+++ b/browsers/bot-detection/stealth.mdx
@@ -68,6 +68,7 @@ Anti-detection is the platform default, so you can freely mix in your own networ
 
 - **BYO proxy, keep CAPTCHA solver** — launch a stealth browser with your own [proxy](/proxies/overview) via `proxy_id`. Replaces the ISP default; CAPTCHA solver stays loaded.
 - **BYO proxy, no CAPTCHA solver** — launch a non-stealth browser with your own `proxy_id`. Full anti-detection config, no managed proxy or CAPTCHA extension.
+- **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.
 - **Disable the default proxy at runtime** — on a running stealth browser, set [`disable_default_proxy`](/proxies/overview#disable-default-proxy-on-stealth-browsers) to route directly while keeping the CAPTCHA solver.
 
 ### Stealth with your own proxy