fix: add browser User-Agent to fix CF 403s on openai_compat backends#13
Closed
briepala wants to merge 1 commit into
Closed
fix: add browser User-Agent to fix CF 403s on openai_compat backends#13briepala wants to merge 1 commit into
briepala wants to merge 1 commit into
Conversation
- Add UC_BROWSER_UA env var (default: modern Chrome UA) - Inject User-Agent + Accept-Language in openai_compat paths, the Auto Router classifier, model discovery, and passthroughs - Route-level "headers" overrides still take precedence - Shortened the related comments
3 tasks
Owner
OnlyTerp
pushed a commit
that referenced
this pull request
Jun 11, 2026
- PR #13: browser User-Agent (UC_BROWSER_UA) for openai_compat upstreams - Issue #15: orchestrator_worker in /healthz, ultracode status, docs - Issue #14: tool-only assistant content=null, context-length error hints, tests PRs #11 and #12 were already merged to main; this branch carries only the delta. Co-authored-by: Cursor <cursoragent@cursor.com>
Owner
|
Closing in favor of #16 (rebased integration branch now contains this fix cleanly on top of main). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cloudflare-protected providers (e.g. crof.ai) were rejecting requests with
"Error 1010: browser_signature_banned" because the proxy used Python's
default urllib User-Agent.
The same API keys + endpoints worked fine from droid/Factory because those
clients send a real browser UA.
crof.ai models (kimi-, deepseek--crof, mimo-*, etc.) now work the same as
they do in droid/Factory.
Tested:
scripts/doctor.pypasses, direct proxy requests to crof modelssucceed and return real responses.