Proxy Flow

Zero-config local proxy and split-route checker for developer tools.

Run it after starting your local proxy client:

npx proxy-flow

It auto-detects system proxy settings, common local ports, and common proxy clients such as v2rayN, Clash/Mihomo, sing-box, and Shadowsocks. Users do not need to know which proxy app they are using or which port it exposes.

If no proxy is running, Proxy Flow prints a clear prompt instead of failing silently.

Commands

proxy-flow          # one terminal check
proxy-flow watch    # refresh in terminal
proxy-flow web      # local dashboard
proxy-flow --json   # machine-readable report

Example

Proxy Flow

Route    OK    Heuristic split check
TUN      WARN  v2rayN is not running as administrator
Proxy    OK    NL via http://127.0.0.1:10808
Egress   INFO  direct=CN proxy=NL

Routes PROXY 4  DIRECT 3
PROXY   OpenAI API     ok    HTTP 421 599ms
PROXY   Claude         ok    HTTP 403 599ms
PROXY   GitHub         ok    HTTP 200 843ms
PROXY   Cursor         ok    HTTP 200 1733ms
DIRECT  Bilibili       ok    HTTP 200 101ms
DIRECT  Tencent        ok    HTTP 501 96ms
DIRECT  iQiyi          ok    HTTP 200 39ms

What It Checks

• Whether a local proxy is reachable.
• Whether overseas/dev targets are expected to use proxy.
• Whether common China targets are expected to use direct routing.
• Whether v2rayN TUN appears active when v2rayN is detected.
• Whether a browser-based dashboard can visualize the same result.

Platform Support

Proxy Flow is designed for Windows, macOS, and Linux.

| Platform | Detection | | --- | --- | | Windows | WinINET system proxy, process list, TUN-like adapters, common local ports | | macOS | scutil --proxy, ps, ifconfig, common local ports | | Linux/Ubuntu | proxy environment variables, ps, ip link, common local ports |

The network verdict always comes from real curl probes. Local configuration files are optional enhancements, not required.

Supported Proxy Clients

Proxy Flow does not require app-specific setup. It recognizes common process names and ports used by:

• v2rayN / Xray / V2Ray
• Clash / Clash Verge / Mihomo
• sing-box
• Shadowsocks / ShadowsocksR
• Surge, Stash, Quantumult, Shadowrocket where visible to the OS

Notes

Per-domain split routing can only be proven when the local client exposes rules or its generated runtime configuration can be read. Otherwise Proxy Flow shows expected routing and connectivity, and clearly reports that no rule-aware config was detected.