Clarify stealth mode: anti-detection is the platform default

[masnwilliams]

Summary

Updates the docs to reflect that anti-detection optimizations are applied to every Kernel browser by default. Stealth mode is now scoped to two managed services on top of that baseline — the default residential proxy and the automatic CAPTCHA solver — both of which remain opt-out.

This makes BYO-proxy / BYO-CAPTCHA a first-class story: customers can keep their own networking and CAPTCHA tooling without losing the anti-detection baseline.

Changes

• browsers/bot-detection/stealth.mdx — rewrote the intro and added a Bring your own proxy or CAPTCHA solver section documenting the common BYO patterns.
• browsers/bot-detection/overview.mdx — added an Anti-detection defaults section above the Stealth Mode blurb and tightened the Stealth Mode description.
• proxies/overview.mdx — added a Bring your own proxy section showing how to pair a custom proxy_id with a non-stealth browser.
• changelog.mdx — April 19 entry covering the platform change and the doc updates.

Test plan

• Mintlify preview renders all four pages without layout regressions.
• Anchor links in the rewritten stealth page resolve (#bring-your-own-proxy-or-captcha-solver, #disable-default-proxy-on-stealth-browsers).
• Changelog entry shows up correctly above the April 17 entry.

Made with Cursor

---

Note

Low Risk
Low risk: documentation-only updates that clarify existing behavior around anti-detection defaults, stealth mode services, and proxy/CAPTCHA configuration patterns.

Overview
Clarifies in the bot-detection docs that anti-detection Chrome configuration now applies to all Kernel browsers by default, and reframes stealth mode as only adding the managed residential proxy and automatic CAPTCHA solver (both opt-out).

Updates the Stealth Mode and Proxies docs to document common BYO proxy / BYO CAPTCHA setups (including using proxy_id with non-stealth browsers and linking to disable_default_proxy), and adds an April 19 changelog.mdx entry capturing these product/docs changes.

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

[firetiger-agent]

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

Any PR that changes the kernel API. Monitor changes to API endpoints (packages/api/cmd/api/) and Temporal workflows (packages/api/lib/temporal) in the kernel repo

Reason: PR only modifies documentation files (mdx), not API endpoints or Temporal workflows code.

To monitor this PR anyway, reply with @firetiger monitor this.

[cursor]

Risk Assessment: Very Low

This PR changes documentation only (.mdx) across:

• browsers/bot-detection/overview.mdx
• browsers/bot-detection/stealth.mdx
• proxies/overview.mdx
• changelog.mdx

I verified the diff contains copy/content updates and examples only, with no application code, config, auth, infra, dependency, or runtime logic changes.

Why this is very low risk

• No production codepaths modified
• No schema, API, or permission changes
• Small, localized blast radius to docs content
• Behavioral impact is limited to documentation clarity

Approved based on current diff state.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[mintlify]

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

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Apr 19, 2026, 7:54 AM

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

[cursor]

Risk Assessment: Very Low

Re-evaluated the current PR diff after the latest synchronize update.

Scope of change is limited to documentation content in:

• browsers/bot-detection/overview.mdx
• browsers/bot-detection/stealth.mdx
• proxies/overview.mdx
• changelog.mdx

The diff contains copy and guidance updates only (including examples), with no runtime code, configuration, auth/permissions, infrastructure, dependency, or schema changes.

Why this remains very low risk

• No production codepaths modified
• No operational or security boundary changes
• Blast radius is limited to docs clarity/content
• No user-facing behavioral change in the product itself

No additional approval action was taken because the PR is already approved.

  

_{Sent by Cursor Automation: Assign PR reviewers}