Clash Verge Rev: a Tauri GUI for the mihomo core, from release page to TUN mode

What Clash Verge Rev replaces, and for whom

Clash Verge Rev is a continuation of zzzgydi/clash-verge, and the README describes it as a Clash Meta GUI based on Tauri. The thing it replaces is not another proxy protocol. It replaces the text editor. A mihomo configuration is a YAML document with proxies, proxy groups, rules and a tun block, and every subscription update overwrites it. The project's answer is profile management with Merge and Script layers, so a provider's file can be refreshed without losing your local edits, plus syntax hints while you edit. The intended user is a desktop user on Windows, Linux or macOS who wants a window with a proxy group selector and a tray icon, not a daemon they configure once and forget. The README does not present a server or router audience, and that boundary matters more than the feature list.

Tauri 2 shell, mihomo core, and the crates in between

The architecture visible in the repository is three layers. The frontend is TypeScript and Vite under src/, with package.json scripts such as web:dev, web:build, typecheck and test pointing at vitest. The desktop shell is Tauri 2, pinned in the workspace at tauri = { version = "2.11.5" }, and src-tauri/ holds the Rust side that the UI calls into. The proxy work itself is done by the bundled Clash.Meta (mihomo) core, which the README says can be switched to an Alpha build. Between the shell and the core sit separate workspace crates: clash-verge-draft, clash-verge-media-unlock, clash-verge-logging, clash-verge-signal, clash-verge-i18n, clash-verge-limiter, and tauri-plugin-clash-verge-sysinfo. The names are the only documentation here, so treat them as boundaries rather than guarantees: the README does not describe what each crate owns. The practical consequence of a Rust core plus a web UI is that the app is a compiled binary, not a Node process, which is why installation is a package download.

Installing Clash Verge Rev on Windows, macOS and Linux

The README is explicit that installation starts at the release page, and it lists the supported targets as Windows (x64/x86), Linux (x64/arm64) and macOS 11+ (intel/apple). There is no package manager command in the README, no Homebrew tap, no apt repository, and no Docker image. You pick the asset matching your platform and architecture from the release you want. The README separates channels: Stable is described as the formal build for daily use, AutoBuild as a rolling build for testing that may contain defects, and Alpha as deprecated and used to test the release process. That table is the whole channel policy, so if you want reproducibility, take a Stable tag such as v2.5.2 rather than a rolling one. The README points to the documentation site for installation notes and FAQ, and those pages are the place to check for platform-specific steps. Building from source is a separate path, documented for contributors rather than users. After all prerequisites for Tauri are installed, the README gives these three commands:

pnpm i
pnpm run prebuild
pnpm dev

Run them from the repository root. The README notes that pnpm dev preserves the Development Channel's installed service state: an existing service is used, while a previously uninstalled service remains uninstalled and the app starts in Sidecar mode. If you want the isolated development service installed or updated before launch, the README gives pnpm dev:service, and pnpm dev:sidecar forces the unprivileged Sidecar workflow.

First run: profile, system proxy, TUN

On first launch the app has no configuration to route through, so the first real task is importing one. The README lists profile management and enhancement as a feature, alongside visual node and rule editing, so the expected flow is: add a profile from a subscription URL or a local file, let the Merge and Script layers apply your additions on top of the provider's document, then select a proxy group. Once a profile is active, the two switches that change system behaviour are the system proxy and the system proxy guard, and TUN (虚拟网卡, a virtual network adapter) mode for traffic that ignores proxy settings. The README also lists WebDav configuration backup and sync, which is the mechanism for moving a working profile set between machines instead of rebuilding it. Two caveats belong here rather than at the end. TUN mode changes routing at the adapter level, so a misconfigured rule set affects every application, not just the ones you meant to route. And the guard that keeps the system proxy in place is a background behaviour, so if you disable the app without disabling the guard, the README gives no rollback procedure for the proxy settings it wrote.

Where Clash Verge Rev is the wrong tool

The README supports desktop operating systems and nothing else. If you searched for a mobile client, note that the repository describes Windows, Linux and macOS only, and there is no Android or iOS target in the README or in the release channel description. If you want a router build, the same silence applies: no OpenWrt package is mentioned, and the acknowledgement list credits mihomo, which is the component a router build would use, not this GUI. A Docker image is likewise absent; the top-level repository entries include a .devcontainer/ directory, which is a development container for contributors, not a distributable server image, and treating it as one is a common misreading. There is also a maintenance shape worth naming: the last push was on 2026-07-19, and the release notes show v2.5.2 on the same date, with v2.5.1 and v2.5.0 both in May 2026. That is a project that ships in bursts around releases rather than continuously, so a bug filed between releases may sit until the next one.

Clash Verge Rev against mihomo alone and against FlClash

The honest alternative on the same protocol is mihomo itself. The difference is not capability, since Clash Verge Rev bundles the mihomo core; it is the interface. Running mihomo directly means you own the YAML, you restart a process to apply changes, and you have no tray selector, no visual rule editor and no Merge layer unless you build one. Clash Verge Rev trades that control for a GUI, an updater and a bundled core you did not choose the version of. A second comparison is FlClash, which appears in the search data as a direct alternative. Both are cross-platform GUI clients for the same core family, and the repository does not describe their internals, so the deciding factor is interface and packaging: check which platforms each ships for and how each handles profile merging before switching. What Clash Verge Rev adds on top of a plain core is the profile layer and the desktop integration, and that is the whole product.

Licence, forks, and what upgrading costs you

The project is GPL-3.0, stated in the README and in package.json as GPL-3.0-only. For a desktop user this changes nothing about running it. For anyone embedding the code, redistributing a modified build, or shipping it inside a product, the copyleft terms apply to the combined work, and the repository is a continuation of an earlier GPL project, which is consistent with that choice. This is a description of the licence text, not legal advice; read LICENSE and PRIVACY.md before you redistribute anything. Upgrade cost is the part users underestimate. Because the app bundles the mihomo core, a release can move the core version under you, and the README notes that an Alpha core can be selected, which means the routing behaviour you validated can change without your configuration changing. The repository also carries a Changelog.md and a docs/ directory, and those are the places to read before upgrading a working machine. Keep a copy of a known-good profile outside the app, since the README gives no documented rollback path for a release that breaks your setup.

Editorial conclusion

Adopt Clash Verge Rev if you are on Windows x64/x86, Linux x64/arm64 or macOS 11+, you already have a subscription URL or a local profile, and you want profile Merge plus a system proxy or TUN toggle in a desktop window rather than a terminal. Do not adopt it if you need a phone client, a router build, a headless server, or a container image: the README lists only desktop platforms and the repository ships no Dockerfile. Before trusting it with a working setup, verify three things yourself: that the release asset you downloaded carries the project's signature, that the Merge and Script preview shows the rules you expect after it has rewritten your profile, and that the mihomo core version bundled in your build is the one you want, since the README says an Alpha core can be switched in.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes