- Remove automatic proxy detection logic from extension startup
- Remove proxy-detection.ts utility file
- Simplify error messages to suggest enabling http.electronFetch when connection issues occur
- Update documentation to focus on the solution rather than detection
As suggested by @bstrdsmkr, the proxy detection approach was fragile. VSCode extensions cannot directly use Electron fetch - they can only suggest users enable the http.electronFetch setting which tells VSCode itself to use Electron fetch internally.
- Add proxy configuration detection utility
- Show warning when http.electronFetch is disabled with proxy settings
- Improve error messages to guide users to the solution
- Add comprehensive proxy configuration documentation
- Update README with link to proxy documentation
Fixes#6991
