Fix Gemini CLI compatibility with proxy and GOOGLE_CLOUD_LOCATION#200
Merged
Conversation
Two fixes for the Gemini agent: 1. Add GOOGLE_CLOUD_LOCATION and CLOUD_ML_REGION to the google provider's passthrough env vars, and auto-sync between them when only one is set on the host. This ensures the Gemini CLI sees GOOGLE_CLOUD_LOCATION (which it now requires) even when the host only has CLOUD_ML_REGION. The sync also benefits the vertex provider. 2. Pin Gemini CLI to 0.35.3 to work around an upstream proxy bug (google-gemini/gemini-cli#24471) where 0.36.0+ throws "HttpsProxyAgent is not a constructor" when proxy env vars are set. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
Two fixes for the Gemini agent:
Add GOOGLE_CLOUD_LOCATION and CLOUD_ML_REGION to the google
provider's passthrough env vars, and auto-sync between them when
only one is set on the host. This ensures the Gemini CLI sees
GOOGLE_CLOUD_LOCATION (which it now requires) even when the host
only has CLOUD_ML_REGION. The sync also benefits the vertex provider.
Pin Gemini CLI to 0.35.3 to work around an upstream proxy bug
(Proxy defined in environment broken: "TypeError: HttpsProxyAgent is not a constructor" when using proxy options google-gemini/gemini-cli#24471) where 0.36.0+ throws
"HttpsProxyAgent is not a constructor" when proxy env vars are set.
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com