Clash Verge Rev Proxy Modes: How to Choose Rule or Global

Before You Change Proxy Modes

Clash Verge Rev can route traffic in different ways without changing your subscription or replacing your proxy nodes. The mode selector controls how Mihomo—the network core used by the client—decides what to do with traffic it receives. Choosing a mode is therefore about matching your routing behavior to the task at hand, not about selecting a faster server.

This distinction helps explain a common surprise: switching from Rule to Global does not necessarily fix a slow or unavailable connection. The selected proxy node may still be unreliable, the application may not be using the system proxy, or the traffic may not be reaching Clash at all. Before troubleshooting, check that a profile is active, the core is running, and at least one usable proxy node is available.

Clash Verge Rev’s layout and labels can vary between releases and operating systems. In many versions, you can find the mode control on the Proxies page, often near the top of the page or above the proxy groups. Look for options labelled Rule, Global, and Direct. If you do not see them, check the main navigation and the application’s settings rather than assuming that the feature is missing. Some builds may arrange controls differently, and a window that is too narrow can hide or reposition page elements.

1What Rule, Global, and Direct Actually Do

The mode changes how traffic is matched against the active configuration. It does not create proxy servers, change the subscription, or guarantee that every program will use Clash. The table below summarizes the practical effect of each option.

Rule Mode in Practice

Rule is usually the best starting point because it lets the profile decide how different traffic should be routed. A rule might send a particular domain to a proxy group, send local-network addresses DIRECT, or block a category of traffic. If the rules end with a catch-all policy such as MATCH, traffic that did not match an earlier rule uses that final policy. The actual outcome depends on the profile, so two users selecting Rule can get very different results.

When Rule mode behaves unexpectedly, check the active profile and the policy selected for the relevant proxy group. On the Proxies page, groups may be displayed as cards or lists. A group such as “Auto,” “Select,” or a regional group may contain its own node choices. Selecting a group and selecting an individual server are not always the same action: a group can apply its own selection or health-check behavior.

Global and Direct in Practice

Global is useful as a diagnostic test, but it is not automatically a better everyday setting. It commonly applies a global proxy policy or group to traffic, and you may still need to choose a working node inside that group. If the group is set to an unavailable server, switching to Global can make more sites fail, not fewer. Direct is a useful comparison test: if a site works in Direct but fails in Rule, the cause may be a rule or proxy path. If it fails in both, investigate the local connection, DNS, application, or destination instead.

2Choose the Mode That Fits Your Situation

For most users, the right choice depends on whether you want the profile to make decisions automatically or want to temporarily simplify routing. Use the following scenarios as a starting point, then verify the result with a small number of tests rather than changing several settings at once.

• Choose Rule for normal browsing. This is generally the most practical option when your profile includes rules for local, regional, and proxy traffic. It can preserve direct access to local services while proxying destinations that the rules assign to a proxy group.
• Choose Global for a controlled proxy test. If one website fails in Rule mode, select Global and confirm that the global policy points to a working proxy group or node. Test the same page again. If it now works, inspect the profile’s rules and group selection; do not assume that Global must remain enabled.
• Choose Direct to compare against your normal route. This can help determine whether a proxy path is involved in a failure. It is also useful when you need to access a destination directly, provided local network policy and the destination allow it.
• Keep Rule when local and proxied services need different routes. Global can send traffic through a proxy even when a direct connection would be preferable, potentially increasing latency or causing local services to behave differently.
• Do not use mode switching as a substitute for node testing. A mode selects routing behavior; it cannot repair an expired subscription, a disconnected core, an unreachable server, or an overloaded proxy node.

Also consider the application you are testing. A browser may honor the operating system’s proxy settings, while another desktop application may use its own network stack and ignore them. A browser test alone cannot prove that all device traffic is being routed. For a reliable comparison, use the same application, the same destination, and the same network connection while changing only one Clash setting at a time.

3Switch Modes and Verify the Result

Use this walkthrough to change the mode safely and confirm that the setting has the effect you expect. Labels may differ slightly across Clash Verge Rev versions, but the underlying checks are the same.

Now distinguish the mode from the way traffic enters Clash. System Proxy configures the operating system’s HTTP or SOCKS proxy settings so compatible applications can send traffic to the client. It is convenient for browsers and many desktop applications, but it does not force every program to obey those settings. A program that uses a custom proxy, ignores system settings, or sends traffic through a separate network path may not be affected.

TUN creates a virtual network interface and can capture a broader range of traffic, including some applications that do not use the system proxy. It may require administrator privileges or operating-system permission and can interact with firewalls, VPN software, security tools, and other virtual adapters. TUN does not replace the mode selector: traffic captured by TUN is still handled according to the active mode and profile rules. Begin with System Proxy if it covers the applications you use; enable TUN only when you need broader capture and understand the additional permissions.

For a clean test, keep the System Proxy or TUN setting unchanged while comparing Rule, Global, and Direct. Afterward, if an application is still unaffected, investigate whether it uses the system proxy or whether TUN capture is required. This two-part check prevents a common misdiagnosis: changing the mode repeatedly when the application’s traffic never entered Clash in the first place.

4Troubleshoot Connection Problems After Switching

If the connection becomes unreliable after changing modes, use the symptoms to narrow down the cause. Change one setting at a time, wait briefly for the client to apply it, and test a known destination again. If several settings are changed together, it becomes much harder to identify which one helped or caused the problem.

The Mode Change Has No Visible Effect

First check that the core is running and the intended profile is active. Then confirm that the application you are testing actually sends traffic through Clash. With System Proxy, test a compatible browser and check the operating system’s proxy status. With TUN, check that it is enabled and that the required permission was granted. A successful mode change cannot affect traffic that bypasses both entry paths.

Rule Routes a Site Unexpectedly

Inspect the active profile’s rules and policy groups. Rules are evaluated in order, so an earlier domain, IP, or rule-set match can take precedence over a later one. Check whether the destination matches a proxy, direct, or reject policy, and confirm that the relevant group points to the intended node. If the client exposes connection or traffic logs, use them to see which rule and policy handled the request. Avoid editing subscription-managed files until you understand whether your changes will persist after a profile update.

Global Still Fails

Verify the global policy’s selected node and test whether that node is available. A proxy group may have an empty selection, an unavailable server, or a test result that has not refreshed. Try a different known-good node if your service provides one. Also consider whether the destination blocks that proxy’s IP or whether the application has stale DNS or cached session data. Global changes the route, but it does not guarantee that a destination accepts the chosen server.

Direct Still Fails

Check whether the destination is reachable without Clash, whether your local network requires a gateway or sign-in page, and whether another VPN or security product is interfering. Confirm that the application is not configured with its own proxy. Direct mode only bypasses proxy routing for traffic handled by the core; it does not repair a disconnected network or override settings inside every application.

Check DNS and System Settings

If domains fail to resolve, load intermittently, or behave differently after a switch, check the profile’s DNS configuration and inspect available logs for resolution errors. Avoid changing DNS values blindly: a resolver that works on one network may be blocked or unsuitable on another. If you use System Proxy, make sure the operating system still points to Clash after restarting the app. If another VPN or proxy manager changes those settings, temporarily disable the competing tool and test again.

For everyday use, return to Rule unless you have a specific reason to keep another mode selected. Rule mode preserves the profile’s intended split routing, while Global and Direct are most useful when you understand their effect or are isolating a problem. Once you know whether the issue comes from a rule, a node, or traffic capture, make the smallest targeted change and retest.

Download Clash