fix: externalize https-proxy-agent in bundle

[tejakusireddy]

Summary

Fixes #26533.

Externalizes https-proxy-agent from the main esbuild bundle so the Vertex AI / gaxios proxy path can load it through Node's runtime module resolver instead of using the bundled copy.

This avoids proxy-agent runtime failures when HTTP_PROXY / HTTPS_PROXY are set.

Details

The proxy path in gaxios lazily imports https-proxy-agent. When bundled into the CLI output, that dependency can hit bundling/runtime interop problems. Keeping it external preserves the package's normal runtime export shape.

This PR also adds https-proxy-agent to the root runtime dependencies so the published CLI package can resolve the externalized import after installation.

Related Issues

Fixes #26533

How to Validate

• npx prettier --check esbuild.config.js package.json package-lock.json
• npm run bundle
• npm pack
• Installed the packed tarball into a clean temp project
• Verified require.resolve('https-proxy-agent') succeeds from the clean installed package
• npm run preflight
• git diff --check

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any) — no breaking changes
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses runtime proxy failures by externalizing the 'https-proxy-agent' package from the main esbuild bundle. By allowing the package to be resolved via Node's native module resolver, it ensures compatibility with Vertex AI and gaxios proxy paths, resolving issues encountered when environment proxy variables are set.

Highlights

• Externalize https-proxy-agent: Added 'https-proxy-agent' to the esbuild external configuration to prevent bundling issues.
• Dependency Management: Added 'https-proxy-agent' to the root package.json and package-lock.json to ensure it is available as a runtime dependency.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Code Review

This pull request adds the https-proxy-agent dependency to the project, updating both package.json and package-lock.json. Additionally, it marks https-proxy-agent as an external dependency in the esbuild.config.js file. There are no review comments to address, and I have no further feedback to provide.

[gemini-cli]

Hi there! Thank you for your interest in contributing to Gemini CLI.

To ensure we maintain high code quality and focus on our prioritized roadmap, we only guarantee review and consideration of pull requests for issues that are explicitly labeled as 'help wanted'.

This PR will be closed in 7 days if it remains without that designation. We encourage you to find and contribute to existing 'help wanted' issues in our backlog! Thank you for your understanding.

[gemini-cli]

This pull request is being closed as it has been open for 14 days without a 'help wanted' designation. We encourage you to find and contribute to existing 'help wanted' issues in our backlog! Thank you for your understanding.