config.yaml / Project sources
The Clash open-source ecosystem and the Mihomo core
Clash Open Source Hub is an independent resource site covering client downloads, config examples, and troubleshooting. Check each project’s documentation for release notes, maintenance status, and feature support. When reading source code, first distinguish the core that handles network traffic from the client interface that controls it.
Project history: different projects, shared name
The original Clash project brought proxy nodes, proxy groups, and routing rules together in one config. Although the original project is no longer maintained, other community projects continue to build on its config structure and the practices around it. Interfaces, menu paths, and fields in old guides aren’t instructions for today’s clients. Use old screenshots to understand concepts, but check the current project for exact steps.
When migrating an old profile, keep the original file and work from a copy. Then compare common fields, node types, and rule targets. A profile that loads successfully doesn’t necessarily mean every setting will work as it did before. Test the basic connection first, then restore features with more dependencies one at a time; this makes issues easier to pinpoint than rewriting the entire file during migration.
How community projects divide responsibilities: interfaces and traffic handling
Graphical clients typically manage config profiles, system integration, and logs. Even clients built around similar cores can differ in tray controls, startup behavior, background services, and override options. For system authorization or installer issues, start with the client project’s documentation. For rule matching and protocol support, check the core’s documentation.
When reviewing public issue reports, check the operating system and reproduction steps described. The same error message can result from file permissions, system network services, or config syntax. When reporting an issue, share a minimal config snippet, the steps that trigger the error, and relevant logs. Remove node details, subscription URLs, and personal data from logs first.
Core lineage: from Clash.Meta to Mihomo
Mihomo is the project name for the continued development of Clash.Meta. Its public repository is maintained under MetaCubeX and is licensed under GPL-3.0. Clients that support the relevant features can pass the selected config to the core, which handles listening, rule matching, and connection forwarding. A client may also merge its interface settings into the final config, so the imported file may differ from what the core actually loads.
To check whether a field is taking effect, compare the saved config with the effective config provided by the client, then check the core logs. Don’t infer the underlying state from a button label alone. For example, seeing that the system proxy is enabled doesn’t mean the virtual network interface is active; they provide different ways for traffic to enter.
Updates: check the app, core, and subscription separately
An app update changes the client itself; whether it also updates the core depends on the project. Refreshing a subscription updates config content, while rule sets may have their own refresh schedule. The interface may call all these actions “Update,” but each changes something different. If a problem appears, note which item was updated most recently and check the corresponding project’s changelog.
Before making changes, keep a copy of a config that worked before. Afterward, retest a request that used to work. If an issue starts after a subscription refresh, check whether proxy groups or rule references changed. If it starts after an app upgrade, check system permissions and startup logs. Don’t refresh the subscription, overwrite the config, and replace the core all at once just to restore a single connection.