Project history: from Clash to mihomo
Clash began as a proxy core that routes connections by rules. Over time, the community maintained different core forks and graphical Clash clients. mihomo continues the configuration system of the Clash.Meta branch, while Clash Verge Rev carries on development of the Clash Verge desktop interface. Older guides may use names that differ from those on the download page. If the steps don’t match your app, check which project the guide covers instead of searching the current interface for an old setting. Even when two Clash clients can import the same configuration, their menu names, system permissions, and supported fields may differ.
Community resources: release notes and issue discussions
Commit history helps trace code changes, release notes show which changes made it into an installer, and public issue discussions can reveal whether a problem is already known. These serve different purposes: a fix merged into the source code isn’t necessarily included in the current release. When reporting an issue, note your device architecture, operating system, traffic capture method, and outbound mode, then describe the steps to reproduce it, what happened, and what you expected. You can include log excerpts relevant to the error, but remove subscription URLs, account details, internal hostnames, and unrelated browsing records first.
Roles: interface, core, and configuration
A graphical Clash client handles the menu bar, configuration imports, and system integration. mihomo parses the configuration, matches rules, and establishes outbound connections. The configuration file defines settings such as policy groups, rules, and proxy servers. Seeing the main window only confirms that the interface has launched; a successful import doesn’t prove that the system is sending traffic to the core. To investigate, first confirm that the test app created a new connection, then check whether it appears in the Clash client. If there’s no record, check the traffic capture method first. If there is a record but the outbound route is unexpected, review the rule order and selected policy group.
Update scope: app updates and subscription refreshes
Updating the Clash client, updating the core, and refreshing a subscription are three separate actions. Some desktop Clash clients update the core along with the app; others provide a separate core update option. Refreshing a subscription usually only replaces remote configuration content—it can’t fix system permissions or installation issues. Before upgrading, back up local configurations and note the current outbound mode, proxy ports, and bypass entries. After upgrading, keep the existing settings and test with the same app. If you update the app, refresh the subscription, and switch to TUN all at once, it’s difficult to tell which change caused a problem.