Repository navigation
Proxy Optimization
tawroot edited this page Sep 26, 2026
·
1 revision
Antigravity Cleaner utilizes a zero-root, process-level proxy architecture. This ensures you do not need kernel TUN mode, preserving system bandwidth and avoiding system-wide routing conflicts.
The smart launcher automatically detects active local proxies on standard ports:
| Client / Core | Default SOCKS5 Port | Default HTTP Port |
|---|---|---|
| Xray / v2ray / v2rayA | 10808 |
10809 |
| NekoBox / sing-box | 2080 |
2081 |
| Clash / Clash Verge | 7890 |
7890 |
| Hiddify / Custom | 1080 |
- |
-
System Bandwidth Freedom: Local development servers (
localhost:3000, Docker containers, database connections) are never routed through the proxy tunnel. -
Zero Root Privilege: No
sudoor administrator rights required to create virtual network interfaces. -
Remote DNS Resolution (
socks5h): All domain lookups for Google endpoints are resolved by the remote exit node, completely preventing DNS poisoning and location leaks.
Run the built-in diagnostic suite:
ag-cleaner doctor --verboseAll Google Cloud endpoints should report READY or Connected (< 1500ms, Fast) for optimal, interruption-free coding sessions.