Profiles and remote sources
A Profile can come from a remote subscription or a local configuration file. Remote Profiles are easier to refresh, while local YAML is useful for fully manual maintenance.
Clash Verge Rev Guide · Profiles / Proxy / TUN
Start with the first launch, then add a Profile, confirm Mihomo loads it correctly, choose a proxy group and routing mode, and enable System Proxy or TUN. Merge and Script can extend a remote Profile without repeatedly editing the source.
Core concepts
Clash Verge Rev manages Profiles and desktop settings, while Mihomo runs the final configuration. Remote or local config is the source, Merge and Script can transform it, and System Proxy or TUN decides how application traffic reaches Mihomo.
A Profile can come from a remote subscription or a local configuration file. Remote Profiles are easier to refresh, while local YAML is useful for fully manual maintenance.
Nodes, proxy groups, rules, DNS and TUN settings ultimately need to form a valid Mihomo configuration. Legacy Clash fields are not always interchangeable with current Mihomo behavior.
Use Merge to add or override structured fields and Script when configuration arrays or more complex transformations need to be changed without editing the remote source directly.
System Proxy changes the operating system proxy settings. TUN uses a virtual network adapter to capture more traffic and usually requires the Clash Verge Rev service and system permissions.
First setup
The workflow is the same across supported Clash Verge Rev desktop systems: install the correct build, add a Profile, check proxy groups, confirm routing mode, then enable the traffic-control layer your applications need.
Choose the Windows, macOS or Linux build that matches your operating system and CPU architecture, then confirm the app and bundled Mihomo core start normally.
Open Profiles, add a remote source or import local YAML, then make sure the intended Profile refreshes and loads successfully.
Open the proxy view, inspect available groups and nodes, and select the policy required by the routing rules in your active Profile.
Rule mode is the normal choice for policy-based routing. Global and Direct are useful when testing whether a problem comes from rules or the proxy path itself.
Start with System Proxy for applications that follow OS proxy settings. Use TUN when broader traffic capture is needed and the required service permissions are available.
Clash Verge Rev can use remote Profiles or local YAML directly. When a remote source needs persistent local customization, Merge or Script is usually cleaner than editing content that will be replaced on the next refresh.
Use a remote Profile when configuration should refresh from a maintained source. Whether nodes, groups or rules change depends on the content returned by that source.
Remote updatesUse local YAML when you want to maintain the entire Mihomo configuration yourself, including proxy groups, rules, DNS, TUN and provider settings.
Local controlMerge is suited to adding or overriding structured fields. Script is more flexible for arrays and complex transformations such as inserting rules or changing proxy groups.
Config extensionRouting modes
The mode changes how Mihomo handles traffic, but the final path still depends on the active Profile, proxy groups and rules. Mode switching is useful for testing, not a substitute for a correct configuration.
| Mode | Best for | Notes |
|---|---|---|
| Rule | Normal daily routing | Mihomo evaluates the active rules in order and sends traffic to the matching proxy group, DIRECT or another configured action. |
| Global | Temporary single-policy testing | Traffic is handed to the selected global policy, which is useful for checking the proxy path without depending on the normal rule set. |
| Direct | Isolating proxy-related issues | Traffic bypasses proxy routing as much as possible, helping confirm whether a problem comes from rules, nodes or the proxy path. |
Both send application traffic toward Mihomo, but they work at different layers. Start with System Proxy, then use TUN only when applications ignore OS proxy settings or broader traffic capture is required.
System Proxy points the operating system proxy settings to Mihomo's local listener. Most browsers and many desktop applications can use this path without additional virtual-network routing.
TUN uses a virtual network adapter to capture more traffic. In Clash Verge Rev, it depends on the service mode and system permissions, so a failed TUN start should be treated as a service or routing issue first.
Configuration FAQ
These answers focus on Profiles, Mihomo configuration, Merge and Script, routing modes, System Proxy, TUN, ports and platform boundaries.
Not exactly. A Profile is the configuration source managed by Clash Verge Rev. A remote subscription is one common way to create a Profile, but local YAML can also be managed as a Profile.
Use a remote Profile when configuration should refresh from a source. Use local YAML when you want to maintain the whole Mihomo configuration yourself. Both can be combined with Merge or Script.
Refreshing a remote Profile replaces the source content. If you need persistent custom fields or rules, use Clash Verge Rev Merge or Script instead of repeatedly editing the remote result.
Merge is better for adding or overriding structured fields. Script is more flexible when arrays or complex content such as rules and proxy groups need programmatic changes.
Some applications do not read operating system proxy settings or use their own networking stack. Check app-specific proxy settings, then use TUN if broader traffic capture is required.
No. TUN captures more traffic but also adds permissions and routing complexity. System Proxy is usually simpler when browsers and normal desktop applications are the main target.
System Proxy must point to the port Mihomo is actually listening on. If mixed, HTTP or SOCKS ports change, confirm that the operating system proxy settings were updated to the new local address.
Confirm Clash Verge Rev service mode is installed and running, then inspect permissions, DNS and route settings, and conflicts with other VPNs or virtual network adapters.
Clash Verge Rev currently targets Windows, macOS and Linux. Mobile applications that support Clash or Mihomo formats are separate projects and use their own interfaces and permission models.
A latency check measures only one path. Real performance also depends on bandwidth, node load, routing rules, DNS, destination quality and your local network.
Next step
Use the download page to choose the correct Windows, macOS or Linux build. After installation, return to this workflow to add a Profile, review proxy groups, and enable System Proxy or TUN.