Clash Verge Rev: A Tauri-based Clash Meta GUI with Config Merging and Scripting

What Problem It Solves and Who It Is For

Clash Verge Rev addresses the need for a modern, cross-platform desktop interface to the Clash Meta (mihomo) proxy core. The original Clash Verge project was discontinued, and this repository is its continuation. It targets users who want a graphical way to manage proxy profiles, switch nodes, and toggle system proxy or TUN mode without editing configuration files by hand. The intended audience includes everyday users who need a reliable proxy client on Windows, macOS, or Linux, as well as power users who want to customize themes, proxy group icons, and even inject custom CSS. Because it is based on Tauri 2 and Rust, it aims to be lighter on system resources than Electron-based alternatives, though the README does not provide specific benchmarks. If you already use mihomo or Clash Meta configurations, this GUI gives you a visual layer on top of that core.

Core Architecture: Tauri 2, Rust, and Bundled mihomo

The project is built on Tauri 2, which combines a Rust backend with a web frontend. The README explicitly states that it uses a "performance-strong Rust and Tauri 2 framework." The proxy engine is the Clash.Meta (mihomo) kernel, which is bundled with the application. Users can also switch to an Alpha version of the kernel, though the README does not explain how to do that in detail. The architecture is similar to other Clash GUIs: the frontend communicates with the mihomo core via its RESTful API, but the README does not describe that data flow. What is clear is that the application manages the kernel lifecycle, including system proxy and TUN mode. The TUN mode creates a virtual network interface, which requires elevated privileges on most operating systems. The README mentions a "system proxy and guard," suggesting there is a mechanism to keep the proxy settings consistent, but the specifics are not documented in the README.

Getting It Running: Installation and Development Commands

For end users, installation is straightforward: download the appropriate package from the Release page. The README lists support for Windows (x64/x86), Linux (x64/arm64), and macOS 11+ (Intel and Apple Silicon). There are three release channels: Stable, Alpha (deprecated), and AutoBuild. The Stable channel is described as "high reliability, suitable for daily use." AutoBuild is a rolling update channel for testing and feedback, but it "may have defects." For developers, the README gives the commands to run the development server: first install Tauri prerequisites, then run `pnpm i`, `pnpm run prebuild`, and `pnpm dev`. The `pnpm dev` command preserves the Development Channel's installed service state, meaning it reuses an existing service or starts in Sidecar mode if none is installed. There are two additional commands: `pnpm dev:service` forces installation or update of the isolated development service, and `pnpm dev:sidecar` forces the unprivileged Sidecar workflow. This distinction is important for developers who need to test different privilege models.

Configuration Management: Merge and Script Enhancements

A standout feature is configuration management with "Merge" and "Script" enhancements. The README lists "config file management and enhancement (Merge and Script), config syntax hints." This means users can take a base proxy configuration and apply overlays or scripts to modify it without editing the original file. This is useful for users who subscribe to proxy providers and need to inject custom rules or change settings that the provider does not expose. The Merge feature likely allows combining multiple config snippets, while Script allows programmatic modification. The README does not provide syntax examples, so the exact format is not confirmed. However, this approach gives power users a way to automate config tweaks, which is a step beyond simple GUI toggles. The trade-off is that writing Merge or Script requires understanding the Clash config schema and the project's scripting language, which is not documented in the README. For less technical users, this feature may be intimidating, but it is optional.

Customization: Themes, Icons, and CSS Injection

The GUI offers a high degree of visual customization. Users can change theme colors, proxy group icons, and tray icons. More notably, the README mentions "CSS Injection," which allows users to inject custom CSS into the interface. This is a powerful feature for those who want to tweak the look beyond the built-in options. The README shows a preview with dark and light modes, but does not elaborate on the theming system. The ability to inject CSS means the interface is built with web technologies, which is consistent with Tauri's model. However, this also means that users who are not comfortable with CSS will not benefit from this feature. The project also supports custom tray icons, which is a nice touch for users who want their proxy client to blend with their desktop environment. The documentation does not specify how to create or apply these custom icons, so users may need to explore the settings UI or the documentation site.

Limitations and Failure Modes

One clear limitation is the reliance on a third-party kernel (mihomo) that may have its own issues. The README does not provide troubleshooting details beyond pointing to a FAQ page. Another limitation is the release model: the Stable channel is intended for daily use, but the AutoBuild channel is explicitly for testing and may contain defects. This means users who want the latest features may have to accept instability. The project is also a community continuation, which implies that long-term maintenance depends on the activity of the maintainers. The README includes promotional sections for third-party services (an airport and an AI customer service platform), which is unusual for a software project and may raise questions about the project's neutrality. The GPL-3.0 license is a significant constraint for developers who want to embed this code in proprietary projects; they cannot do so without open-sourcing their own code. Finally, the README does not mention any automated testing or CI status, so the reliability of each release is not transparent.

Alternatives and How They Differ

The most direct alternative is the original Clash Verge, which this project continues. The README acknowledges that Clash Verge Rev is based on or inspired by it. The key difference is that Clash Verge Rev is actively maintained, while the original appears to be discontinued. Another alternative is Clash for Windows, which is also mentioned in the acknowledgements. Clash for Windows is a Windows/macOS GUI based on Clash, but it is not built on Tauri; it uses Electron, which typically consumes more memory. The README does not compare performance, but the choice of Tauri suggests a focus on lower resource usage. For users who prefer a command-line approach, they could use mihomo directly without a GUI, but that loses the visual node management and system proxy integration. The unique value of Clash Verge Rev is its combination of a modern UI, cross-platform support, and config enhancement features that are not present in all alternatives.

Maintenance, Licensing, and Upgrade Considerations

The project is under active development, with the latest release v2.5.2 pushed on 2026-07-19. The default branch is `dev`, which indicates that the development version is the primary branch. This is a sign of continuous work, but it also means that the stable releases may lag behind the dev branch. The license is GPL-3.0, which means any derivative work must also be GPL-3.0. This is a copyleft license, so if you modify and distribute the software, you must provide the source code. For internal use, this is not a problem, but for commercial redistribution, it is a serious consideration. The README mentions WebDAV configuration backup and sync, which is a useful feature for keeping settings consistent across machines. However, the README does not specify which WebDAV providers are supported or how to set it up. Upgrading between versions is not documented in the README; users are expected to download new packages from the Release page. The presence of an AutoBuild channel suggests that some users run rolling releases, which may require more frequent updates and potential breakage.

Editorial conclusion

Adopt Clash Verge Rev if you need a cross-platform GUI for Clash Meta with deep customization: CSS injection, custom theme colors, and config enhancement via Merge and Script. It is also a good fit if you want to switch between stable and alpha mihomo kernels. Avoid it if you require a stable, long-term supported tool with a formal release process, since the project is a community continuation with rolling AutoBuild releases that may contain defects. Before adopting, verify the current release's stability on your OS (Windows x64/x86, Linux x64/arm64, macOS 11+), check the FAQ for known issues, and confirm that the GPL-3.0 license aligns with your usage. Also, note the README contains promotional links to third-party services; these are not part of the core project and may affect your trust in the maintainers.

Official sources

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