Skip to content

feat: enable Verified Browser Mode and residential proxies by default#1

Open
shubh24 wants to merge 1 commit into
browserbase:mainfrom
shubh24:feat/enable-verified-and-proxies
Open

feat: enable Verified Browser Mode and residential proxies by default#1
shubh24 wants to merge 1 commit into
browserbase:mainfrom
shubh24:feat/enable-verified-and-proxies

Conversation

@shubh24

@shubh24 shubh24 commented Jun 3, 2026

Copy link
Copy Markdown

Problem

createSession() sends browserSettings.stealth: true, but stealth is not a recognized field in the Browserbase session-create API, so it is silently ignored. As a result the app creates plain sessions — no advanced stealth, no proxies — despite the README claiming "advanced stealth enabled by default." These sessions get stopped by Cloudflare's "Performing security verification" interstitial and similar anti-bot challenges.

Fix

Send the correct fields:

  • browserSettings.verified — Verified Browser Mode (advanced stealth)
  • top-level proxies — Browserbase-managed residential proxies (note: this is a top-level field, not nested under browserSettings)

Both default to ON and can be disabled via env vars:

BROWSERBASE_VERIFIED=false   # disable Verified Browser Mode
BROWSERBASE_PROXIES=false    # disable residential proxies

Changes

  • src/main/browserbase.ts — replace the no-op stealth field with verified + top-level proxies, both env-toggleable
  • src/shared/types.ts — update SessionConfig (proxies, browserSettings.verified)
  • .env.example — document the two new toggles
  • README.md — correct the stealth feature description

Notes

  • verified and residential proxies require a Browserbase plan that includes them; on plans without them the API will reject or ignore the flags.
  • Verified locally: app boots, creates a session with verified: true + proxies: true (status RUNNING, accepted by the API), connects over CDP, and loads pages.

Docs: Verified mode · Proxies

🤖 Generated with Claude Code

Sessions previously sent `browserSettings.stealth: true`, which is not a
recognized Browserbase session field and was silently ignored — so sessions
ran without advanced stealth or proxies, and got blocked by Cloudflare and
similar anti-bot challenges.

This wires the correct fields:
- `browserSettings.verified` (Verified Browser Mode / advanced stealth)
- top-level `proxies` (Browserbase-managed residential proxies)

Both default to ON and can be disabled via the BROWSERBASE_VERIFIED /
BROWSERBASE_PROXIES env vars. Note these features require a Browserbase plan
that includes them.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant