fix: preserve proxy settings across MCP client environments - #1
Merged
Merged
Conversation
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.
MCP clients can filter inherited proxy variables, causing connections to fail around 10.7 seconds even when the same terminal can reach Grok. This adds opt-in
config --proxy/--proxy-from-envexport for all six client formats, while preserving existing configuration output when neither flag is selected.The PR also adds an optional
doctor --networkcheck (one unauthenticated metadata GET, no inference) and safe transport cause codes torequest_uncertain. It documents proxy setup and distinguishes endpoint reachability from authentication. Proxy credentials are never exported; there are no automatic retries or billing changes.Validation: all 34 offline source tests passed on Windows / Node 26.8.1, including a real Node child using the official MCP SDK minimal environment and a loopback proxy. No additional model calls or redundant local release/hash audits were performed for this PR. The previously authorized local environment repair restored a real search with five citations.
The new flags are source-only pending a later release. This PR does not merge itself, publish npm, or modify the immutable 0.1.0 release.