Outbound proxy

The Outbound proxy decides what network egress OSW uses to reach upstreams. Configure it in Settings → Network → Outbound proxy.

Three modes

Mode	Behavior
Direct	Reach the upstream directly, through no proxy.
Follow system	Use the operating system's current proxy settings.
Custom	Fill in a proxy address manually.

When you need it

The upstream is only reachable through a corporate proxy.
You need to pin model requests to a particular egress.
Direct connections to upstreams on the local network are unstable, and a proxy is steadier.

Which traffic bypasses the proxy

Telemetry does not use your proxy

Anonymous usage telemetry never uses the user-configured outbound proxy; it connects directly and independently. That way your proxy logs never show a target you didn't expect, and a misconfigured proxy doesn't make telemetry fail permanently. See Local-first & secrets.

Unrelated to protocol conversion

The outbound proxy only changes the network egress, not the protocol. For protocol handling see Supported protocols.

How a wrong proxy shows up

A wrong custom proxy address makes every upstream request fail to connect, showing up as widespread network errors in request logs. Switching back to direct quickly confirms whether the proxy is the problem.

Once configured, watch every request with Request logs.