Clash Verge FAQ

Load a remote subscription or local profile, confirm that Mihomo parses it, then check whether the expected proxy nodes, proxy groups and routing rules appear. After the configuration loads, use system proxy for applications that honor OS proxy settings or TUN when broader traffic entry is required. Current and previous desktop builds are listed on GitHub Releases.

Windows builds are separated by x64 and ARM64. macOS builds are separated by Apple Silicon and Intel. Linux releases also vary by CPU architecture and DEB / RPM format. Check the current release filenames and platform requirements before using a build.

Clash Verge uses Tauri, whose Windows interface depends on WebView2. If the process starts but the panel stays blank, the tray icon does nothing, or the UI closes immediately, check WebView2, Windows version and the relevant release notes or Issues before treating the problem as a profile or Mihomo fault.

Clash Verge is a proxy client, not a proxy service provider. Proxy nodes, proxy groups and routing rules come from the profile or subscription you load. If the proxy view is empty, confirm that a remote subscription or local profile is loaded and that Mihomo can parse it successfully.

TUN creates a virtual network interface and changes operating-system routing, so Clash Verge needs privileged service capabilities to manage it. The exact permission flow differs across Windows, macOS and Linux, but it is separate from simply opening the desktop application or using system proxy.

No. Clash Verge manages profiles, proxy nodes, proxy groups, routing rules and local traffic entry. It does not provide proxy nodes, subscription services or network access plans. Remote profiles and proxy infrastructure come from third-party services or infrastructure you manage separately.

Add the remote subscription URL from the profile area or load a local configuration file. Some flows also support the clash:// URL scheme. After loading the profile, confirm that Mihomo accepts it and then inspect the nodes, proxy groups and routing rules it defines.

Direct changes to a profile generated from a remote subscription can be overwritten when the source refreshes. Keep persistent changes in a separate configuration layer, such as visual rule edits, Extension Config for YAML changes or Extension Script for JavaScript-based transformations.

Extension Config is YAML-based and merges or overrides fields in the generated profile. Extension Script uses JavaScript for more flexible transformations. Older Clash Verge documentation called these Merge Config and Script Config; prepend/append rule editing is now handled through the profile's visual rule editor.

Yes. Use the visual rule editor when you want to insert rules around a subscription's existing rules, or use Extension Config/Extension Script when the generated profile needs broader changes. Mihomo evaluates routing rules in order, so rule placement is just as important as rule syntax.

The project privacy policy states that configuration, credentials and logs are stored in the application's local data directory. Those files can include subscription URLs, proxy credentials and connection metadata, so back them up carefully and review them before attaching anything to a public bug report.

System proxy changes the operating-system proxy settings and only affects applications that use those settings. TUN creates a virtual network interface and can route a broader set of application traffic through Mihomo, including software that does not read the system proxy configuration.

Check TUN permissions, the virtual network interface, Mihomo runtime state, system routes, firewalls and other networking tools. If the fault remains unclear, search GitHub Issues with the operating system, client version and exact error text.

Rule mode lets the active Mihomo rules choose DIRECT, a proxy group or another policy for each connection. Global mode routes traffic through the global proxy policy, while Direct mode bypasses proxy routing. Switching modes temporarily can help separate a routing-rule problem from a node or connectivity problem.

System proxy only affects applications that read the operating system proxy settings. Command-line tools, games and applications with their own network stack may connect directly unless they are configured explicitly or traffic enters Mihomo through TUN.

Not necessarily. The latency test measures response time to the configured test URL and is useful for comparing reachability and round-trip delay. Throughput depends on many other factors, including route quality, server load, congestion and the destination you are actually using.

An abnormal shutdown can leave the operating-system proxy setting enabled even though Clash Verge is no longer running. Reopen Clash Verge and disable system proxy normally, or turn the manual proxy off in your operating system's network settings.

Project documentation states that configuration, credentials and logs remain on the local device and that telemetry, analytics, crash reports and usage data are not collected. Remote subscriptions, proxy nodes, DNS services, update checks and WebDAV can still connect to separate endpoints configured by the user or the client.

Clash Verge is the local desktop client. A subscription service provides a remote profile, and proxy nodes carry traffic when a rule selects them. Those are separate layers, so node quality, service pricing, traffic retention and provider policies are not controlled by the Clash Verge client.

The application hands traffic to the local Mihomo core through system proxy or TUN. Mihomo evaluates the active routing rules and then chooses DIRECT, REJECT or a proxy policy. Only traffic assigned to a proxy policy is forwarded through the selected proxy server; DIRECT traffic leaves through the local network normally.

In Rule mode, Mihomo evaluates the current routing rules from top to bottom. Domain rules, IP results, process rules and rule providers can send different connections to different policies. A profile update, DNS result change or rule-provider refresh can therefore change which rule matches the same destination. Version-specific implementation details can be checked in the project repository.

Local application data is normally reused across updates, but a major version can include migrations or compatibility changes. Back up the application data directory or create a WebDAV backup before a significant upgrade, and read the release notes when moving across older versions.

Stable Releases and AutoBuilds belong to the Clash Verge client release layer, while newer development builds can track more recent commits. Mihomo Stable / Alpha belongs to the proxy-core layer. Client release channel and core channel should be recorded separately when troubleshooting.

GitHub Releases keeps historical version tags, release assets and version notes. Before moving across versions, back up important local profiles and extension data, then check architecture, migration notes and compatibility differences.

Configure your own WebDAV server in Clash Verge, create a configuration backup, then restore that backup after a reinstall or on another desktop. The WebDAV server receives the backup file, which can contain sensitive profile information, so its credentials and privacy policy matter.

The project currently targets Windows, macOS and Linux desktop systems. Android and iOS clients belong to separate projects and may implement a different subset of Mihomo-compatible features.

Current Releases separate desktop builds by operating system, CPU architecture and release format. The available combinations differ across Windows, macOS and Linux. Exact operating-system requirements and release formats should be checked against the current release notes.

Clash Verge is the desktop GUI. Mihomo, formerly known as Clash.Meta, is the proxy core that handles protocols, DNS, routing rules, proxy groups and traffic forwarding. “Clash” is the broader configuration and client ecosystem name, which is why users commonly refer to Clash profiles, Clash rules and Clash-compatible configurations when working with Mihomo.

Yes. The project is GPL-3.0 open source. Building it locally requires Node.js / Corepack / pnpm, Rust and platform-specific Tauri dependencies; use the repository README and current CONTRIBUTING.md rather than relying on commands from an older release.