TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/klzgrad/naiveproxy/llms.txt
Use this file to discover all available pages before exploring further.
naive binary exposes standard SOCKS5 and HTTP proxy interfaces locally, which means any application or tool that understands those protocols can route its traffic through NaïveProxy without modification. Beyond direct use, a growing ecosystem of GUI clients and mobile apps has built-in support for NaïveProxy, making it easy to get started without touching the command line.
GUI Clients
The following clients offer graphical interfaces with native NaïveProxy support. No manual configuration of thenaive binary is required — these applications manage it for you.
v2rayN
A full-featured Windows GUI client that supports NaïveProxy alongside other proxy protocols. Manage servers, switch profiles, and monitor traffic from a system tray icon.
Exclave
An Android client with NaïveProxy support, providing a streamlined mobile experience for managing proxy connections on the go.
husi
An Android proxy client that integrates NaïveProxy among its supported protocols, targeting users who need flexible, multi-protocol support on Android.
NekoBox for Android
A versatile Android proxy app based on the sing-box core, supporting NaïveProxy and a wide range of other proxy protocols in a unified interface.
Using NaïveProxy as a Local Proxy Backend
Oncenaive is running, it acts as a standard SOCKS5 or HTTP proxy server on your local machine. Any application that supports proxy configuration can be pointed at it directly — no special integration or plugin is required.
curl
socks5h scheme tells curl to resolve hostnames through the proxy rather than locally, which is important for both privacy and correctness when the destination domain would not resolve from your network.
git
System-wide environment variables
Many command-line tools and runtimes respect the standardhttp_proxy and https_proxy environment variables. Setting them in your shell session routes all supported traffic through naive:
~/.bashrc or ~/.zshrc) to make them persistent across sessions.
Notes for Downstream Maintainers
Do not track the
master branch. The NaïveProxy repository rebases from a new root commit for every Chrome release, meaning the master branch history is rewritten regularly. Tracking it in a downstream project will break your version control history.Use stable release tags instead. Each tag corresponds to a tested release, and short release notes are provided alongside every tag to summarize what changed.