Cause (Documented platform behavior): Explicit SDK limitations.
Fix status: documented_behavior
Limitations:
- Forwarding-proxy workaround is general practice, not from Stagehand docs
Other error fragments:
- setInputFiles(): file is larger than the 50 MiB upload limit
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/browserbase/stagehand/70f4e91f1983677c1e8ca9a86f0b738f828d059a/packages/sdk-ts/src/browser/localBrowser.ts (official_docs, unknown, documented_behavior): Validation throws for authenticated proxies.
- https://raw.githubusercontent.com/browserbase/stagehand/70f4e91f1983677c1e8ca9a86f0b738f828d059a/packages/sdk-ts/src/fileUpload.ts (official_docs, unknown, documented_behavior): setInputFiles throws RangeError above 50 MiB.
Search phrasings: Stagehand Authenticated local browser proxies are not supported; stagehand setInputFiles 50 MiB upload limit
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Browser launch or upload throws.
- Context
- Product: Stagehand Component: Stagehand TS SDK localBrowser / fileUpload Operation: Local Chrome with username/password proxy, or uploading large files Affected versions: unknown Environment: unknown Packages: @browserbasehq/stagehand 4.x (source at time of mining) Trigger: proxy.username/password set for localBrowser; or file > 50 MiB in setInputFiles.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Authenticated local browser proxies are not supported yet
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Stagehand v4 local browser] 'Authenticated local browser proxies are not supported yet' / setInputFiles 50 MiB limit
Recommended action: Use an unauthenticated local proxy (e.g. a local forwarder that injects credentials) or Browserbase proxies; split/compress uploads under 50 MiB.
Option: Use an unauthenticated local proxy (e.g. a local forwarder that injects credentials) or Browserbase proxies; split/compress uploads under 50 MiB. [evidence: documented_workaround]
Applies when: Local Chrome with username/password proxy, or uploading large files
Steps:
1. Run a local forwarding proxy without auth
2. Or use Browserbase-managed proxies
3. Keep upload files under 50 MiB
Expected: The error no longer appears.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 8f1b9ca0-01bd-4fe8-bdb2-8af06c5844c3
- Proposed action
- Recommended action: Use an unauthenticated local proxy (e.g. a local forwarder that injects credentials) or Browserbase proxies; split/compress uploads under 50 MiB. Option: Use an unauthenticated local proxy (e.g. a local forwarder that injects credentials) or Browserbase proxies; split/compress uploads under 50 MiB. [evidence: documented_workaround] Applies when: Local Chrome with username/password proxy, or uploading large files Steps: 1. Run a local forwarding proxy without auth 2. Or use Browserbase-managed proxies 3. Keep upload files under 50 MiB Expected: The error no longer appears.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.