feat(web): add HTTP proxy support via environment variables (#913)#1479
feat(web): add HTTP proxy support via environment variables (#913)#1479huboqiang wants to merge 1 commit intoMoonshotAI:mainfrom
Conversation
334d7a2 to
7790072
Compare
…AI#913) Support HTTP/HTTPS proxy configuration through standard environment variables: HTTPS_PROXY, https_proxy, HTTP_PROXY, http_proxy. This enables Kimi CLI to work properly in environments that require proxy access to reach the API. Fixes MoonshotAI#913 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
7790072 to
d28deb0
Compare
|
@RealKai42 Several developers have tried to "enable env http_proxy & socks_proxy feature" including this PR: #1479, #1465, #1236 (mine). It's really a problem for the users in enterprise with proxy-based internet access. Please take a look at the PR, thanks a lot. |
|
I really need the proxy configuration feature. The company's servers are on the internal network and need to go through a proxy server to access external resources. |
|
I need the proxy configuration feature badly @RealKai42 |
@wangzhanxd I think only the oauth is blocked due to missing |
Related Issue
Closes #913
Description
In environments that require HTTP/HTTPS proxy access (e.g., corporate networks or restricted regions), Kimi CLI previously could not
connect to the API because aiohttp.ClientSession was created without proxy configuration.
This PR adds support for standard proxy environment variables, allowing users to configure proxy settings without modifying code or
configuration files:
Changes
configuration
Checklist
I have read the CONTRIBUTING document.
I have linked the related issue, if any.
I have added tests that prove my fix is effective or that my feature works.
I have run
make gen-changelogto update the changelog.I have run
make gen-docsto update the user documentation.