[STG-2560] docs: replace deprecated advancedStealth with verified

[aq17]

Summary

Docs pass to replace the deprecated advancedStealth browser setting with verified across the Stagehand docs. User-facing examples and tables should show the current canonical name.

Reported by Alex on Slack, pointing at v3/configuration/browser → "Advanced Browserbase Configuration Example".

Changes

v3 docs

• packages/docs/v3/configuration/browser.mdx — code sample now uses verified: false instead of advancedStealth: false
• packages/docs/v3/integrations/mcp/setup.mdx — Optional query params table + Local CLI flags table swapped to verified / --verified
• packages/docs/v3/integrations/mcp/configuration.mdx — CLI flags table swapped, "Advanced Stealth" tab retitled to "Verified" with a deprecated-alias note, security best-practices bullet updated

v2 docs — same fixes for the v2 mirror

Not touched

• packages/docs/sdk-api-reference-labels.js — this is a snake_case rewriter driven by the live OpenAPI wire field; advancedStealth is still part of the API spec, so the mapping is intentional.
• Generated SDK code across stagehand-{java,go,python,ruby} and sdk-node — regenerated from OpenAPI, not human-authored docs.
• packages/core/lib/v3/v3.ts and packages/core/lib/v3/types/public/api.ts — deliberately keep advancedStealth as a backwards-compat alias (see the @deprecated comment on isAdvancedStealth in v3.ts).

Test plan

Docs-only diff — no code paths touched. Verified with git diff that only the six intended MDX files change and every remaining advancedStealth mention is either an intentional deprecated-alias note or unchanged code that reflects the API's continued support of both names.

Requested by: alexander@browserbase.com
Linear: https://linear.app/browserbase/issue/STG-2560/docs-replace-deprecated-advancedstealth-with-verified-across-stagehand
Slack thread: https://browserbase.slack.com/archives/D0AHY8DEQPM/p1783960618071569

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4f839d0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cubic-dev-ai]

All reported issues were addressed

Confidence score: 5/5

• Safe to merge after the addressed issues were fixed.

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

1 issue found and verified against the latest diff

Confidence score: 5/5

• In packages/docs/v2/integrations/mcp/configuration.mdx, the renamed tab currently omits migration guidance for --advancedStealth, which could confuse existing MCP users and lead to misconfigured setups when they copy updated docs—add a deprecated-alias note that maps old usage to --verified before merging.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/docs/v2/integrations/mcp/configuration.mdx">

<violation number="1" location="packages/docs/v2/integrations/mcp/configuration.mdx:166">
P3: Existing MCP configurations using `--advancedStealth` have no migration/backwards-compatibility guidance in this renamed tab. Add the deprecated-alias note so users know to switch new configurations to `--verified` without assuming existing ones are broken.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P3: Existing MCP configurations using --advancedStealth have no migration/backwards-compatibility guidance in this renamed tab. Add the deprecated-alias note so users know to switch new configurations to --verified without assuming existing ones are broken.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/docs/v2/integrations/mcp/configuration.mdx, line 166:

<comment>Existing MCP configurations using `--advancedStealth` have no migration/backwards-compatibility guidance in this renamed tab. Add the deprecated-alias note so users know to switch new configurations to `--verified` without assuming existing ones are broken.</comment>

<file context>
@@ -157,21 +157,21 @@ Enable Browserbase proxies for IP rotation and geo-location testing.
+[Learn more about Verified Identity](https://docs.browserbase.com/features/stealth-mode#advanced-stealth-mode)
 
-**Note:** Advanced Stealth is only available for Scale Plan users.
+**Note:** Verified Identity is only available for Scale Plan users.
 </Panel>
 
</file context>

Suggested change

	**Note:** Verified Identity is only available for Scale Plan users.
	**Note:** Verified Identity is only available for Scale Plan users.
	**Deprecated alias:** `--advancedStealth` remains supported for backwards compatibility; use `--verified` in new configurations.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
stagehand	🟢 Ready	View Preview	Jul 13, 2026, 5:22 PM

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