WebFetch fails when internet access is available only through a system proxy
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- desktop, networking
Research direction
Start by locating the WebFetch implementation and comparing its proxy handling with the GitHub Copilot CLI behavior described in the issue. Reproduce the failure with a system-configured proxy; done means WebFetch can retrieve external URLs through that proxy without the host-resolution error.
Written by the indexing model from the issue text.
Description
Short summary
In environments where outbound internet connectivity is provided via a system-configured proxy, the WebFetch tool fails to access external URLs and returns a host resolution error.
Affected version or release
v1.1.22
Installation context
No response
What happened?
When the GitHub Copilot agent attempts to retrieve content from a URL using the WebFetch tool, the request fails with the following error:
WebFetchBlockedUrlError: No such host is known. (os error 11001)
This occurs even when internet connectivity is available and functional through a properly configured system proxy.
Steps to reproduce
- Configure internet access through a system proxy.
- Start a GitHub Copilot agent session.
- Ask the agent to research a topic that requires fetching information from an external URL.
- Observe that the agent invokes the WebFetch tool and the request fails with:
WebFetchBlockedUrlError: No such host is known. (os error 11001)
Expected behavior
When a system proxy is configured, WebFetch should honor the operating system's proxy settings and route outbound requests through the proxy.
The behavior should be consistent with GitHub Copilot CLI, where web access works successfully in the same environment using the configured proxy.
Additional context
WebFetchBlockedUrlError: No such host is known. (os error 11001)
GitHub Copilot CLI can successfully perform web access in the same environment through the configured proxy.
The issue appears specific to the WebFetch implementation not honoring system proxy settings, all other features in Copilot app works.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/app
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
seagle0128/doom-modeline#834 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
robotframework/RIDE#3068 ·