Clash Party: A Mihomo GUI with AI Node Selection and WebDAV Backup

What Clash Party Solves and Who It Targets

Clash Party is a desktop GUI for Mihomo, the Clash Meta core. It targets users who want a visual interface for managing proxy subscriptions, rules, and TUN mode without editing YAML files by hand. The README highlights features like one-click Smart Core rule overrides, a TUN mode that works without service mode, and deep Sub-Store integration. The intended audience is proxy users who want convenience: automatic node selection, easy subscription management, and a polished UI with multiple color themes. The project is written in TypeScript and licensed under GPL-3.0, which matters if you plan to redistribute modified versions.

The Smart Core Mechanism: AI-Driven Node Selection

The standout feature is Smart Core, which the README describes as a rule override that uses an AI model to automatically select the optimal node. The documentation link points to a dedicated guide at clashparty.org/docs/guide/smart-core, but the README itself does not explain how the AI model is trained, what data it uses, or how it evaluates node performance. This is a black box from the material. The feature is presented as a one-click override, meaning it likely rewrites or injects rules into the Mihomo config. The repository ships with both a Smart kernel and the standard Mihomo kernel, so users can switch between the two. The lack of technical detail in the README is a gap: if you are evaluating this for production use, you would need to read the full guide to understand the AI's decision criteria and whether it respects your own routing preferences.

Getting It Running: Installation and Configuration

The README points to the official documentation at clashparty.org for installation and usage. It does not list direct commands or build steps in the repository description. Based on the release tags, binaries are distributed via GitHub Releases, so typical installation would involve downloading the latest release for your platform. The configuration approach is GUI-driven: you can modify most common Mihomo settings, use the override feature to rewrite config files arbitrarily, and back up or restore configurations via WebDAV. The README mentions a one-click TUN mode that requires no service mode, which suggests the GUI handles the necessary privileged operations internally. For developers who want to build from source, the repository is TypeScript-based, but no build instructions are given in the cleaned README. You would need to inspect the repo or docs for exact commands.

Limitations and Failure Modes

The most obvious limitation is the heavy promotion of a specific paid proxy service, '狗狗加速', at the top of the README. This affiliate link and discount code make the documentation feel less neutral and raise questions about whether the project's development priorities align with user interests. It is a red flag for a tool that handles network traffic. Another limitation is the Smart Core feature's opacity: without detailed documentation, you cannot predict when the AI might select a node that violates your intended policy, such as a specific geographic exit or a rule-based split. The TUN mode that works without service mode is convenient, but it may have platform-specific constraints that are not covered in the README. The project is relatively young, with v2.0.2 released in August 2026, so the API and configuration format could change between versions, breaking existing setups.

Alternatives: Comparing Approaches

The most direct alternative is Clash Verge Rev, another Mihomo GUI that is widely used. The key difference is that Clash Verge Rev does not include an AI-based node selector; it relies on traditional rule sets and manual node selection. Clash Party's Smart Core is a different approach because it automates node choice using a model, which could reduce manual tweaking but also introduces unpredictability. Another alternative is the original Clash for Windows, though it is no longer actively maintained. Clash Verge Rev focuses on a stable, configurable GUI with a large community, while Clash Party differentiates itself through Smart Core and WebDAV backup. If you need deterministic routing, a traditional GUI gives you more control. If you want AI-driven convenience, Clash Party is the only option in this comparison.

Maintenance and Upgrade Cost

The project is actively maintained, with releases in July and August 2026, and the default branch is named 'smart_core', indicating ongoing development on that feature. The GPL-3.0 license means any derivative work must also be GPL-3.0, which is fine for personal use but a consideration if you embed it in a proprietary product. The upgrade cost is moderate: because the GUI handles config overrides, you need to re-test your own rules after each update, especially if Smart Core changes its model or behavior. The README mentions WebDAV backup, which lowers the risk of losing configuration during upgrades. However, the documentation is thin in the README, so you will likely rely on the official docs site for migration notes. There is no mention of a changelog in the material, so you would need to check release notes manually to understand what changed between versions.

Editorial conclusion

Adopt Clash Party if you want a Mihomo GUI that bundles Smart Core for AI-based node selection, offers a no-service-mode TUN, and integrates WebDAV backup and Sub-Store. Avoid it if you distrust the affiliate-heavy README or need a GUI with a longer, more battle-tested history. Before adopting, verify the Smart Core behavior on your own proxy setup, check the GPL-3.0 obligations if you plan to modify or redistribute, and review the official docs at clashparty.org for installation steps and configuration details.

Official sources

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