IA proxies

[juecd]

Description

• Moves Proxies under the Browsers resource -> "Bot Anti-Detection" section to explain Stealth mode vs. customizable proxies
• Puts custom proxies first, before Kernel-managed but configurable proxies
• Removes the "proxies" page that was mostly duplicative of Proxies Overview
• A few style things so the pages mirror existing styles

---

TL;DR

Reorganized the proxy and stealth documentation into a new "Bot Anti-Detection" section under "Browsers" to improve clarity and information architecture.

Why we made these changes

The previous documentation structure separated Proxies from Browsers, making it difficult for users to understand how they relate, especially in the context of Stealth Mode. This change creates a more logical flow by grouping all anti-detection features together, clarifying the relationship between the automated Stealth mode and more advanced, customizable proxy configurations.

What changed?

• Restructured Documentation: Created a new "Bot Anti-Detection" navigation group under "Browsers" and moved the "Stealth" and all "Proxies" pages into it.
• Removed Redundant Content: Deleted the browsers/proxies.mdx page, as its content was largely duplicative of the "Proxies Overview" page.
• Improved Content Clarity:
  • Updated the "Stealth Mode" doc to better explain its included features (proxy configuration, reCAPTCHA solver) and link to the detailed proxy pages.
  • Refined content across all proxy pages (overview.mdx, custom.mdx, isp.mdx, etc.) for better readability, consistency, and style.
  • Reordered proxy types to present custom proxies first.

Validation

{List of tests or validations performed}

^{Description generated by Mesa. Update settings}

[mesa-dot-dev]

Performed full review of 88531d7...5d6fd7e

Analysis

1. The removal of browsers/proxies.mdx eliminates duplicate content but potentially sacrifices some specific content on detection avoidance capabilities that may be valuable for users.

2. While grouping proxies under "Bot Anti-Detection" creates a logical hierarchy, it might create an expectation that proxies are primarily for anti-detection when they serve other purposes too.

3. Placing "Custom" proxies first may optimize for users with existing proxy infrastructure but could create a steeper learning curve for new users who might benefit from seeing simpler options first.

4. Though internal navigation links improve discoverability, the PR doesn't mention if there's a clear path for users to understand which proxy type best suits different use cases.

Tip

⚡ Quick Actions

This review was generated by Mesa.

Actions:

• Configure your agents

Slash Commands:

• /review - Request a full code review
• /review latest - Review only changes since the last review
• /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
• /help - Get help with Mesa commands and configuration options

^{8 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings}

[sjmiller609]

TY!