Three connection modes
How PAC, explicit proxy and TUN differ and how to choose.
The connection mode decides which apps hand their traffic to CoderBoost. Whatever the mode, only targets on the resource list go through edge nodes; everything else is untouched.
| Mode | How it works | Good for | Extra setup |
|---|---|---|---|
| Auto proxy (PAC, default) | Writes only the system auto-proxy address | Browsers and desktop apps that follow system proxy settings | Terminal tools need environment variables |
| Explicit proxy | A local proxy port (HTTP + SOCKS5) | Apps you configure yourself: terminals, IDEs, scripts | Enter the proxy address in the app |
| Virtual adapter (TUN) | Takes over per resource at the system level | Programs that ignore proxy settings, programs in containers | Requires the system helper |
How to choose
- Most people: PAC plus terminal environment variables is enough.
- A program never uses the proxy (some Electron apps, game-engine downloaders, CLIs with their own network stack): try TUN.
- You only want a few tools to use it: explicit proxy.
What happens when you stop
When you disconnect, the client restores your previous system proxy settings. If another app changed the system proxy while you were connected, the client does not overwrite it.
Linux
cnb mode pac # or explicit / tun
cnb connect --mode tun