mihomo, Clash Verge Rev, and FlClash: How They Fit into the Clash Project Ecosystem
Learn how Clash forks evolved after the original core was discontinued, how mihomo differs from graphical clients, and how to choose among projects based on their roles and maintenance status.
The Clash Project Ecosystem: Core Forks vs. Client Forks
mihomo is a proxy core, while Clash Verge Rev and FlClash are graphical clients that use mihomo. They are not three versions of the same project. Older guides that mention Clash Meta refer to the core before it was renamed mihomo. The “Rev” in Clash Verge Rev refers to the continuation of the original Clash Verge desktop client; it has nothing to do with the Clash Meta rename.
| Project | Layer | Relationship to other projects |
|---|---|---|
| Original Clash | Proxy core | The source of the original configuration syntax and rule model; the project is discontinued |
| Clash Meta / mihomo | Proxy core | A core fork developed within the Clash ecosystem; renamed mihomo after Clash Meta |
| Clash Verge Rev | Desktop client | A continuation of the Clash Verge desktop app, with mihomo integrated |
| FlClash | Cross-platform client | An independent Flutter client that uses mihomo; it is not a mobile version of Verge Rev |
The original Clash stopped being maintained in 2023. Clash Meta already existed before the original project was discontinued; it was not a replacement built from scratch afterward. Common settings such as proxy-groups and rules carried over to mihomo, but a shared syntax heritage does not mean every extension field is compatible in both directions. When an older guide mentions Clash, Clash Premium, or Clash Meta, first identify the core it targets before assuming its settings can be reused.
What the Core, Client, and Operating System Each Do
mihomo uses the active configuration to open listening ports, parse proxy groups and routing rules, handle DNS, and choose an outbound for matching connections. The graphical client imports and updates subscriptions, saves configurations, generates overrides, starts the core, and displays logs. The operating system determines whether app traffic reaches the core through the system proxy, TUN, or a platform VPN interface. If any of these three layers is not working, the app may show “connected” while applications still have access problems.
Tell These Three Settings Apart by Their Ports
For example, in a local configuration, mixed-port: 7890 can provide a combined HTTP and SOCKS proxy listener, while external-controller: 127.0.0.1:9090 is the local control interface. They serve different purposes: setting your browser proxy to 127.0.0.1:9090 does not turn the control interface into a proxy. The ports 7890 and 9090 are examples; when troubleshooting, check the ports used by the running instance rather than assuming an older guide's values are the client defaults.
- Subscription imported, but the core fails to load: Open the startup log. Check for YAML parsing errors or unsupported fields, then make sure every policy group referenced by a rule exists.
- The core is running, but only some apps use the proxy: Check whether those apps respect the system proxy. Enabling the system proxy does not route all device traffic through it.
- Connection problems after enabling TUN: First confirm that the TUN interface was created, then check for routing or DNS issues. Fake-IP is a DNS enhancement mode; its toggle does not tell you whether TUN is routing traffic.
Choosing Between Clash Verge Rev and FlClash
Desktop First: Check Clash Verge Rev's System Integration
Clash Verge Rev is a desktop client for Windows, macOS, and Linux. If you manage multiple configurations, inspect connections, or switch between the system proxy and TUN in your daily workflow, start by checking the installer and permission requirements for your operating system. For long-running use, test whether closing the window minimizes the app to the tray or exits it, then confirm the proxy state after a restart. Service mode, administrator permissions, and launch at startup are separate settings; installing a service does not enable the system proxy. If TUN stops working after an upgrade, first check that the installed service matches the current client version rather than switching subscriptions.
Across Devices: Check FlClash Releases for Your Platform
FlClash uses Flutter for its interface and may suit people who want a similar experience on Android and desktop. Still, check the release assets for each platform before downloading. For example, Windows builds may be available for x64 and ARM64, while Android users should match the APK to their device architecture or choose a universal package explicitly listed on the release page. Do not assume the project provides an installer for every platform supported by Flutter. Android VPN permission, per-app routing, and background battery restrictions are mobile OS integration issues; desktop behavior does not verify that the app works as expected on a phone.
No Desktop Environment: Run mihomo Directly
If a device only needs a background process and you can manage the configuration, startup method, and logs yourself, running mihomo directly makes it easier to track the active configuration file and core version. The trade-off is that you must handle subscription updates, process supervision, and permissions. If you mainly want to switch policy groups or view connection logs in an interface, choosing a graphical client first and checking its core version is usually more straightforward than installing the core separately.
Maintenance Status: Check Archives, Releases, and the Version Actually Running
The discontinuation of the original Clash is part of the project's history. mihomo is a separately maintained core project that followed it; Clash Verge Rev and FlClash release their clients independently and do not share a release schedule. To decide whether an installer is worth upgrading, check the relevant project's repository and release history for your platform. One project's activity does not reflect the state of the entire ecosystem.
- Verify the project identity. The core repository is
MetaCubeX/mihomo, the desktop client repository isclash-verge-rev/clash-verge-rev, and the FlClash repository ischen08209/FlClash. Assess similarly named mirrors and downstream forks separately from the original projects. - Check whether the repository is archived, then review Releases for stable versions, prerelease labels, and change notes. Recent commits show that code has changed, but do not prove that a new installer is available for your operating system.
- Note the client version before upgrading. After the upgrade, confirm the version actually running in the client's core information or startup log. For a standalone deployment, run
mihomo -vto check the binary being invoked; the binary in your system path may not be the one launched by a graphical client. - Read change notes according to the problem you're addressing. For configuration load failures, check core compatibility first. For tray exits, subscription updates, or service installation issues, look at fixes for the client and the relevant platform.
Migrating from an Older Clash Client: Verify the Active Configuration and Traffic
Before migrating, back up your subscription URL, local YAML file, and override rules. A subscription is usually just a configuration source; selected policy group states, client-generated overrides, and system proxy settings may not be stored in the same file. If your old client has custom direct-connection rules or dedicated DNS settings, don't delete your backup after importing only the subscription. Subscription URLs may contain access tokens, so redact them before sharing logs or configurations.
- Stop the old instance. Quit the old client and check for background services to avoid two instances competing for the same listening port or system proxy settings.
- Load the configuration before enabling traffic capture. Make sure every name referenced by
RULE-SETexists inrule-providers, and check that the rule-set format and behavior type match. Once the startup log is clear, enable the system proxy or TUN as needed. - Verify routing in the connection log. In Rule mode, visit one test domain expected to connect directly and another expected to use the proxy. Check which rule each connection matches and its final outbound. Rules are evaluated in order; an early
MATCHprevents later rules from being reached. - Restart and check again. Confirm that the client reloads the intended configuration and that policy group selections have not reverted to a different outbound. Then verify separately whether a subscription update overwrites local changes.
When choosing a client, start with your operating system and how you plan to use it, then check configuration compatibility against the mihomo version actually running. For troubleshooting, narrow the issue down to the configuration, core, or operating system traffic capture layer; this is more useful than cycling through installers based on project names.