From Clash to Clash Meta and mihomo
Clash built an ecosystem around rule-based proxies and YAML configuration. After the original project was discontinued, the community continued developing related cores and GUI clients. Clash Meta was later renamed mihomo, so tutorials, configuration notes, and client settings may use both names. The projects are related, but that doesn't mean every old field, new protocol, and client feature is fully compatible.
If a field has no effect, check the client's About or Core page to confirm which core is running, then consult its documentation. Older guides can explain the basics, but shouldn't be used to determine what current versions support. DNS, TUN, and rule providers in particular may work differently depending on core capabilities and client integration.
GUI clients and cores are maintained separately
GUI clients such as Clash Verge Rev and FlClash focus on configuration management, interface, system proxy, and permission integration. mihomo parses configuration, matches rules, and establishes connections. Clients and cores follow their own maintenance schedules, so a change in the app interface doesn't necessarily mean the core's behavior changed too. Choose a download based on your platform and needs; the Clash name alone doesn't guarantee that two clients have the same features.
Open-source licenses explain the terms for using, modifying, and distributing code; they don't mean different projects share a publisher. Our brand is used to organize downloads and Chinese-language guides. Check each project's own materials for its maintainer. For an overview, read How Clash, Clash Meta, and mihomo are related before deciding which configurations to migrate or keep.
Handle software updates separately from subscription updates
Updating a client usually affects its interface, system integration, or bundled core. Updating a subscription mainly changes nodes, policy groups, and rules. If connection problems start after a subscription update, compare the configuration changes before reinstalling the app. Before upgrading the client, export your current configuration, note overrides and proxy ports, and confirm the new version loads everything before removing old files.
Subscription management involves service URLs and account permissions. A client supporting a protocol doesn't mean every link from every source is trustworthy. Only import configurations from sources you know and are authorized to use. When asking for help publicly, redact access parameters, account details, and node credentials from subscription URLs. This site provides configuration and usage references; it doesn't distribute “free nodes” or guarantee third-party service availability.
Browse the source code and license
mihomo is licensed under GPL-3.0. You can explore its implementation, issue discussions, and release notes in the public repository. If you plan to build it yourself or distribute a modified version, read the license and relevant dependency notices in full. If you just want to use a client, start with a GUI app; you don't need to set up a build environment first.
The command on the right downloads the public source code to a local directory. It doesn't install a client, establish a proxy connection, or change your network settings. Run it in a terminal with Git installed. If you're looking for the meaning of a field, open the configuration reference or glossary instead. To verify implementation details, consult the source alongside the project documentation.