Copilot can't access web even after changed setting

[gmaksimovic]

Select Topic Area

Question

Copilot Feature Area

VS Code

Body

I'm using Copilot in VSCode and I have a Copilot Pro subscription. I was asking it to check some documentation and it said that it cannot access external websites, which was weird since I recalled it doing that before.
Googled a bit and was told to check the setting in Github, which I did. It was disabled, so I enabled it and tried asking it again, same result.

I've tried changing models, tried restarting VSCode a few times. Tried signing out and in to Github in VSCode. Nothing has made a difference. Any suggestions what might be wrong and how I could fix it?

[Akash1134]

Hi @gmaksimovic,

Thank you for reaching out about the web browsing capability in GitHub Copilot. I understand you have a Copilot Pro subscription and have enabled web browsing in your VS Code settings, but Copilot still cannot access external websites.

How Web Browsing Works in GitHub Copilot

Web browsing in GitHub Copilot is accessed through Copilot Chat rather than directly through completions. Here's how to properly use this feature:

1. Enable the setting in your GitHub account (not just VS Code):

   • Go to GitHub.com and sign in
   • Click your profile photo in the top right
   • Select "Settings" → "GitHub Copilot"
   • Make sure "Copilot access to Bing" is enabled in the dropdown menu

2. Use the correct syntax in Copilot Chat:

   • Option 1: Use the @github #web command followed by your query
     Example: @github #web What is the latest LTS of Node.js?

   • Option 2: Use natural language with the @github participant
     Example: @github Search the web to find the latest GPT model from OpenAI

Troubleshooting Tips

• Ensure you're using Copilot Chat (not just the inline completions)
• Verify you're signed in with the same GitHub account that has the Copilot Pro subscription
• Try restarting VS Code after enabling all settings
• Make sure you have the latest version of the GitHub Copilot extension

If you've followed these steps and are still experiencing issues, please let me know what specific error messages you're seeing, and I'll be happy to investigate further.

Hope this helps!

[gmaksimovic]

When I try that I just get "Response contained no choices".

[satyamjhablockdev]

Hi! A few things can cause Copilot Chat in VS Code to say it can’t access the web even after you flip the setting. Run through this checklist (top-to-bottom) and it usually clears it up:

1) Make sure the right place is enabled

• Personal account: GitHub → Settings → Copilot → Chat & web → turn on Use web results in chat.
• Org account: Your org owner/admin must enable web for the org. If the org policy disallows web, your personal toggle won’t override it.

2) Update VS Code & extensions

• VS Code to latest stable.
• Extensions: GitHub Copilot and GitHub Copilot Chat → Update/Reload.

3) Re-establish auth cleanly

In VS Code Command Palette:

GitHub: Sign out
Copilot: Sign out
Developer: Reload Window
GitHub: Sign in
Copilot: Sign in

(If you see multiple accounts in Accounts panel, remove the stale ones.)

4) Confirm you’re using Chat’s web tool (not inline)

Inline completions don’t browse. In the Copilot Chat panel, either:

• Click the globe/web toggle (if shown), or
• Ask explicitly: “Search the web for …” or “Use web to find …”.

5) Check network/proxy

Copilot’s web search uses external endpoints. Corporate proxies/VPNs often block them.

• In VS Code settings, set your proxy (http.proxy) if needed.
• Allowlist typical endpoints like api.githubcopilot.com, api.github.com, and your search provider (e.g., *.bing.com).
• Try outside VPN to rule this out.

6) Clear extension state (quick nuke)

1. Disable → re-enable GitHub Copilot Chat.
2. If still stuck: uninstall/reinstall the Chat extension.
3. Optional: delete the extension’s Global Storage folder (VS Code will recreate it).

7) Cross-check on the web

Open copilot.github.com (or GitHub.com → Copilot Chat) and try “Search the web for …”.

• Works in browser but not VS Code? It’s a local VS Code/extension or network config issue.
• Doesn’t work anywhere? It’s account/org policy ask your org admin or contact GitHub Support.

[adam-versed]

I am also experiencing this issue - the agent chat insists it doesnt have access to web search capabilities, seems to be a conflict in that its not in its available tools list - i have it enabled via the github portal and used the @github #web syntax you suggested.

[behnamsattar]

I'm using an organization account and I don't see the access control under my organization Copilot settings anywhere! Copilot in Agent mode in the chat interface in VSCode clearly can't read web pages...

[alucarded]

I also have the same issue. Enabled web search in policies settings long time ago. The Copilot Chat extension was updated multiple times since then and I have restarted VS Code multiple times. I have Pro sub.

[yashasam]

hu @gmaksimovic

1. Clear Cached Copilot Tokens and Sessions
   Corrupted or expired authentication tokens can sometimes cause problems.
   Open the Command Palette in VS Code (Ctrl+Shift+P or Cmd+Shift+P).
   Run the command: GitHub: Sign out.
   Then, run the command: GitHub: Clear all sessions.
   Close VS Code completely.
   Delete the .github-copilot folder:
   On Windows: %USERPROFILE%.github-copilot
   On Linux/WSL: ~/.github-copilot
   Reopen VS Code and sign back in to GitHub when prompted. Make sure the permissions requested include read:user, repo, workflow, user:email, and copilot.
2. Verify Authorized OAuth Apps on GitHub
   Ensure Copilot is authorized correctly in your GitHub account settings.
   Go to your GitHub Authorized OAuth Apps settings.
   Find "GitHub Copilot" and revoke its access.
   Go back to VS Code and try signing in to GitHub Copilot again, allowing it to re-authorize from scratch.
3. Check for Proxy or Firewall Interference
   If you're on a corporate network, VPN, or have a local firewall enabled, it might block Copilot's access to external websites or the Copilot service.
   Try connecting from a different network (e.g., your phone's hotspot if allowed) to rule out network-specific issues.
   Temporarily disable your VPN or local firewall to see if it resolves the problem.
   Check VS Code's proxy settings:
   Open File > Preferences > Settings.
   Search for "proxy".
   Ensure any proxy settings are correctly configured for your network. Copilot might use a slightly different proxy mechanism than VS Code's default, especially if your proxy URL starts with https://, which is not currently supported by GitHub Copilot.
   If you're using a proxy, you might need to include your credentials in the proxy URL format like http://USERNAME:PASSWORD@10.203.0.1:5187/, according to GitHub Docs.
   Check for certificate-related errors if you have a corporate proxy that intercepts secure connections. Your IT department might need to configure it to not intercept secure connections, or you might need to install custom certificates in your operating system's trust store.
   Try ignoring certificate errors in VS Code's proxy settings (by deselecting Proxy Strict SSL), but be aware of the security implications.
4. Collect and Review Copilot Diagnostic Logs
   VS Code and the Copilot extension provide diagnostic logs that can contain more specific error messages about connection failures.
   Open the Command Palette (Ctrl+Shift+P).
   Run the command: GitHub Copilot: Collect Diagnostics.
   An editor tab will open with diagnostics information. Look for errors related to network connectivity, server connection failures, or specific error codes.
   You can also view the GitHub Copilot output channel:
   Open the Output panel (Ctrl+Shift+U).
   From the dropdown menu (top-right of the panel), select "GitHub Copilot" or "GitHub Copilot Chat". Look for errors like "GitHub Copilot could not connect to server" or "read ETIMEDOUT".
5. Check System Clock Synchronization (especially for WSL/Linux)
   Token-based authentication can be sensitive to system time differences. Ensure your system clock is correctly synced.

[doxiado-dev]

To resolve the issue with GitHub Copilot not accessing external websites in VS Code despite enabling the web browsing setting, try the following steps based on available information:

1. Verify GitHub Account Settings:

   • Ensure the "Copilot access to Bing" setting is enabled in your GitHub account. Go to GitHub.com, sign in, click your profile photo (top right), select Settings > GitHub Copilot, and confirm that "Copilot access to Bing" is enabled in the dropdown menu.
   • Verify that you’re signed into VS Code with the same GitHub account that has the Copilot Pro subscription.

2. Use Correct Syntax in Copilot Chat:

   • Web browsing in GitHub Copilot is accessed through Copilot Chat, not inline completions. Use one of these methods:
     • Option 1: Use the @github #web command followed by your query. Example: @github #web What is the latest LTS of Node.js?
     • Option 2: Use natural language with the @github participant. Example: @github Search the web to find the latest GPT model from OpenAI.
   • Ensure you’re typing these commands in the Copilot Chat interface, not the editor.

3. Check VS Code and Extension Versions:

   • Confirm you’re using the latest version of VS Code and the GitHub Copilot extension. Update them via the Extensions tab or by downloading the latest VS Code release.
   • If the issue persists, try switching to the pre-release version of the Copilot extension for potential bug fixes. In the Extensions tab, click the Switch to Pre-release version button.

4. Network and Proxy Settings:

   • Network restrictions (e.g., corporate firewalls or proxies) might block Copilot’s web access. Test on an unrestricted network (like a mobile hotspot) to rule this out.
   • If on a corporate network, ask your IT administrator to whitelist the following domains:
     • https://github.com
     • https://api.githubcopilot.com
     • https://copilot-proxy.githubusercontent.com
   • Configure proxy settings in VS Code if needed:
     • Go to File > Preferences > Settings, search for “Proxy,” and set your proxy address under http.proxy. Optionally, set http.proxyStrictSSL to false if you face SSL issues (not recommended for security reasons).

5. Check Logs for Errors:

   • View Copilot logs in VS Code to identify specific errors:
     • Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P on Mac) and run Developer: Set Log Level..., setting it to Trace for the Copilot Chat and Window channels.
     • Then, open the Output tab, select GitHub Copilot or GitHub Copilot Chat from the dropdown, and review the logs for errors like “Response contained no choices” or network issues.
   • Run the Developer: GitHub Copilot Chat Diagnostics command from the Command Palette and check the output for network or authentication issues.

6. Re-authenticate GitHub Account:

   • If authentication is the issue, sign out and back in:
     • In VS Code, go to the Accounts menu (bottom left), click your profile, and select Sign out.
     • Sign in again via the GitHub login prompt. If the login flow freezes, use the GitHub CLI to authenticate: run gh auth login in a terminal and follow the browser-based authentication.
   • If the “Refresh your credentials” option is missing, remove and re-add your GitHub account in VS Code.

7. Firewall and Antivirus:

   • Temporarily disable your firewall or antivirus to check if they’re blocking Copilot’s connections. If this resolves the issue, add exceptions for VS Code and Copilot-related processes in your firewall settings.
   • For Windows, go to Control Panel > Windows Defender Firewall > Allow an App and add your IDE. For macOS, go to System Settings > Network > Firewall > Options and allow your IDE.

8. Reinstall Copilot Extension:

   • Uninstall the GitHub Copilot extension from the Extensions tab, restart VS Code, and reinstall it. This can resolve corrupted extension issues.

9. Check GitHub Service Status:

   • Visit githubstatus.com to ensure Copilot’s services are operational. If there’s an outage, wait for it to be resolved.

If none of these steps work, the issue might be related to a bug or a specific configuration in your environment. Consider:

• Testing on a different machine or user account to isolate the issue.
• Reporting the issue on GitHub’s Community Discussions or VS Code’s issue tracker, including:
  • The exact error message (e.g., “Response contained no choices”).
  • Logs from the GitHub Copilot or Copilot Chat output channels.
  • Steps to reproduce the issue.
  • Your VS Code version, Copilot extension version, and OS details.

[daemon-001]

Maybe that site uses bot detection and rate limiting, or is protected from web scraping like LinkedIn. Automated requests without browser-like headers can get blocked or throttled. So, while you can read it in a normal browser, automated tools like Copilot can’t pull it in directly unless they fully simulate a browser session. Copilot also has its own policy for how it retrieves data from webpages.
Since you hvbeen told that you done it before, may be that site updated its policy from backend

Fix: You can manually paste all the raw text from that page into Copilot and then ask it for what you need.

[AlexKovynev]

maybe somebody know is it right that web search not work pro plan?