Clash Verge Rev: Bypass the Proxy for One Website

First check: this is a system proxy exception, not a TUN rule

Your browser already works through Clash Verge Rev, but you want one website to connect directly without passing through the local proxy listener. A system proxy exception can do that. It does not make every other website connect directly, and you do not need to rewrite your subscription for a single hostname.

This guide uses the English interface of Clash Verge Rev v2.5.2 on Windows 10/11, x64 or ARM64. It is not the discontinued Clash for Windows client. The project remains maintained, but these instructions have been checked only against v2.5.2; menus may change in later versions. The ordinary system proxy must already work, Use PAC Mode must be off, and TUN, another VPN or a browser-specific proxy must not be handling the test traffic. If your network depends on any of those settings, keep the existing setup and do not apply these steps blindly.

This is a guide to adding your first exception: you currently use the default bypass list and have not maintained an additional custom list. The instructions include a stopping point if an existing custom configuration appears, so that you do not overwrite someone else's exceptions.

How this differs from a DIRECT rule: an application that follows the Windows proxy settings handles the system proxy exception, so the request can avoid Mihomo altogether. A DIRECT rule chooses a direct connection after a request has entered the core. Both may result in direct access, but their scope and connection logs differ. This guide does not configure PAC, TUN or a WSL proxy.

Open the settings and record the default list first

Go to Settings → System Setting and click the settings icon beside System Proxy to open System Proxy Setting. Do not change the proxy host, listening port or guard interval just to add a website. The default list includes more than localhost: it also contains patterns for local and LAN addresses. Removing them can change local access that already works.

Confirm that the system proxy is enabled and Use PAC Mode is off. If the editing controls are unavailable, check these prerequisites instead of disabling format validation.
Check that Always use Default Bypass is currently on. Privately record the entire displayed default list and the switch state.
Turn off Always use Default Bypass, then compare the editable list that appears with the default list you just recorded.
Continue only if the lists match. If the switch was already off, or turning it off reveals other saved custom entries, click Cancel and keep the original configuration. Do not delete those entries to make the list match this example.

A displayed default list does not prove there are no saved custom entries: in v2.5.2, enabling the default switch displays only the defaults; the editable contents appear when you turn it off. Comparing the two views is therefore essential. On a company- or school-managed device, also confirm that the administrator allows this website to bypass the proxy.

Add one hostname, then save

The example hostname below is example.com. Replace it with the actual hostname you are authorized to access and have confirmed should connect directly. Start with one host instead of immediately extending the exception to every subdomain.

Keep every existing default entry. Leave Always use Default Bypass off and Validate Proxy Bypass Format on.
Enter the target hostname, such as example.com, in the input below Proxy Bypass Settings:.
Click New or press Enter. Confirm that the hostname has become a separate list entry and is no longer just an uncommitted draft in the input.
Click Save and watch for errors. Reopen the settings afterward to confirm that the entry remains and the default switch is still off.

The input field and the list are separate states. Typing a hostname and immediately clicking the dialog's Save button is not enough to establish that it was added to the list. Saving also updates the system proxy asynchronously, so the dialog closing is not proof of success. Avoid making these changes during a long download, meeting or remote session.

If you use Advanced text editing, separate multiple Windows exceptions with semicolons, ;. The visual list handles the platform's separator for you. This guide uses list editing so that you do not need to copy a complete block of default addresses by hand.

Enter a hostname, not a full URL or page path

Entry	Use it here?	Reason
`example.com`	Yes, replacing it with your target host	Use one explicit hostname for a limited test
`www.example.com`	Check separately if the destination uses www	Do not treat the root domain and different subdomains as one entry
`https://example.com/account`	No	The scheme and page path are not part of the hostname expected here
`DOMAIN-SUFFIX,example.com,DIRECT`	No	This is core rule syntax, not a Windows proxy exception
`192.168.0.0/16`	Do not copy this	This version's Windows bypass validator does not accept this CIDR notation

A website may redirect to another host, while its login and static resources may use other domains. An exception for one host does not mean that every request belonging to the service connects directly. Check the actual hostname in the address bar and the host used by a failed request before deciding whether another entry is necessary. Do not disable validation to force an entry through, and do not use * to match every address.

Check both the exception and traffic that should still use the proxy

After saving, confirm that the system proxy remains enabled, then have the browser establish a new connection to the target website. Existing connections may retain their previous route. If necessary, close the relevant browser processes and reopen the browser, taking care of any unsaved work in tabs first.

Check the target host: reopen the bypass settings and confirm that the entry matches the hostname actually being visited, including any different destination after a redirect.
Make a control request: visit a website known to require the current proxy and not included in the exception list. Check the Clash Verge Rev connections page to confirm that this traffic still enters the core and uses the expected outbound connection.
Interpret direct-connection evidence carefully: if the target request appears in the core's connections as DIRECT, it still entered the core. Conversely, a missing log entry alone does not prove that bypass worked: cached pages, connection reuse and an application's own proxy settings can affect the observation.

For a precise check, combine the browser's network records with access logs from the destination service when you are authorized to view them, and check the path of new requests. A page loading is a functional check, not proof that every resource uses the intended exit. If an extension or organization policy controls the browser's settings, identify which proxy configuration is actually in effect instead of repeatedly reinstalling the client.

How to restore the default bypass scope

These steps apply only if you confirmed earlier that the default bypass was originally enabled and turning it off revealed no additional custom entries. They restore the default bypass scope, not every byte of the configuration file. They do not delete subscriptions or nodes.

Reopen System Proxy Setting and leave the default switch off for now.
Clear the editable bypass list. If it contains many entries, switch to Advanced text mode to clear it, then confirm that the editing area is genuinely empty.
Turn Always use Default Bypass back on and click Save.
Check the default list and system proxy status again, then test a local page and a website that previously worked through the proxy.

Do not assume that merely turning the default switch on undoes the change: saved custom contents do not necessarily disappear. The recovery procedure here first clears the custom field and then uses the defaults. If you already had other custom entries, restore them from your own record instead; do not use the clearing procedure.

A useful website exception is narrowly scoped, preserves the old list and produces a result you can verify. Once you have confirmed that this particular host should connect directly, keep that setting. There is no need to change DNS, nodes and proxy mode at the same time.

Official sources and version scope

Version numbers, filenames, and interface labels can change. Confirm them in the linked project documentation before making changes.