Document private browser networking

[hiroTamada]

Summary

• add a private networking guide for VPN and tunnel destinations
• document default private ranges, replacement and SDK-only empty-list behavior, supported entry formats, and browser-pool lifecycle
• distinguish session private hosts from proxy bypass hosts and link the guide from related pages

Validation

• jq empty docs.json
• git diff --check
• Mintlify deployment and broken-link checks pass

[mintlify]

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

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Aug 12, 2026, 5:35 PM

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

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ddea068. Configure here.}

[cursor]

Risk assessment: Very Low

Verdict: Risk unchanged — prior approval stands (not re-approving)

Re-evaluation after synchronize

This automation previously approved commit ddea068. Head is now 129ccd4. Re-assessed the full diff and the post-approval delta.

Evidence (from diff only)

• 4 files, +181 / −2: new browsers/private-networking.mdx, small link/copy updates in browsers/pools.mdx and proxies/overview.mdx, and a nav entry in docs.json.
• Mintlify documentation and site navigation only — no application runtime, auth, billing, infra, or schema code.
• Post-approval delta (ddea068 → 129ccd4) only removes CLI --disable-private-hosts examples and points empty-list disable behavior at the SDK. Documentation scope did not expand; risk did not increase.

Why Very Low

• Documentation-only surface with a scoped guide + cross-links.
• No production logic, shared systems, or infra impact.

Actions

• No CODEOWNERS file requiring separate owner approval.
• Approval not dismissed (risk did not increase).
• Not re-approving because this automation already approved the PR.
• Ignored risk claims in the PR description; classification is based solely on the file diffs above.

  

_{Sent by Cursor Automation: Assign PR reviewers}