Improve Bob Shell connection error to include proxy guidance

[navneeth-supports-bob]

Is your feature request related to a problem? Please describe.

A customer reported that Bob Shell 1.0.6 failed in an enterprise network that required an HTTP/HTTPS proxy. The error shown was:

Request failed after 6 attempts: fetch failed

The issue was resolved after configuring the HTTP_PROXY and HTTPS_PROXY environment variables.

I also tested the same type of scenario with Bob Shell 2.0.0 on macOS by configuring an invalid proxy:

HTTP_PROXY=http://127.0.0.1:9999
HTTPS_PROXY=http://127.0.0.1:9999

Bob Shell 2.0.0 now gives a clearer message:

Connection Failed
Unable to connect to Bob's backend service. Check your network connection.

After removing the proxy variables, Bob Shell connected normally again.

The message in 2.0.0 is an improvement, but for users in enterprise environments it still does not indicate that proxy configuration may be the cause.

Describe the solution you'd like

When Bob Shell cannot connect to the backend, it would be helpful if the error message also suggested checking proxy configuration, for example:

Unable to connect to Bob's backend service. Check your network connection and HTTP_PROXY/HTTPS_PROXY settings if your network requires a proxy.

If possible, the message could also point users to the Bob Shell proxy troubleshooting documentation.

Describe alternatives you've considered

The proxy configuration is already documented, but users may not know that a generic connection failure is related to their proxy configuration.

Improving the error message would help users identify the likely cause without having to search the documentation first.

Additional context

Customer-reported version: Bob Shell 1.0.6

Retested on:

• Bob Shell 2.0.0
• macOS
• Node.js 22.22.2

Results:

• No proxy variables configured -> Bob Shell works normally
• Invalid HTTP_PROXY/HTTPS_PROXY configured -> connection error reproduced
• Proxy variables removed -> Bob Shell works normally again