From Clash to mihomo
The Clash ecosystem has long used YAML to describe inbounds, outbounds, and rules. mihomo continues the core project formerly known as Clash.Meta. Older resources commonly use earlier names. When you see an old screenshot or parameter in documentation, first check which project it refers to. Similar names can help with searching, but they don’t prove a field is still supported or that two installers come from the same maintainer.
Open-source licensing and project roles
The mihomo source repository is licensed under GPL-3.0. Visit the upstream repository to browse the code, change history, and issue discussions. This license applies to the core project; it doesn’t mean every GUI client uses the same license. GUI projects maintain their own interfaces, system integrations, and release packages. Subscription providers maintain subscription content; updating a subscription doesn’t replace the client or install a new core on your system.
The GUI and the active configuration
The core handles inbounds, selects outbounds according to rules, and manages connections. A GUI client may also combine subscriptions, overrides, and global settings before passing the result to the core. If rules appear in a config file but don’t take effect in the app, first confirm which config is active, then check how overrides are applied, and finally review the connection log. Looking only at the original file in an editor can miss settings added by the client.
Which release notes should you check before upgrading?
When changing installers, start with the client’s release notes. For changes to rule syntax, DNS behavior, or TUN support, check the changelog for the core you use as well. Before updating, record your current config and traffic capture method, and save copies of local rules and overrides. After updating, test against the same destination. If you’re only adding one rule, saving and testing it separately makes changes easier to pinpoint than updating the app, rule sets, and subscription all at once.