Subscriptions supply nodes. A profile organizes the groups, rules and core parameters passed to Mihomo and can reference one or more subscriptions. Downloading a subscription does not start it. For basic use, “Quick Start” creates a linked profile; select it in “Overview” and start the core. Identify the running profile before changing its groups or rules.
Prefer a verified ZIP backup for your OS and architecture on this site’s download page. Use its official latest-download link for other architectures or newer releases. For Windows, choose amd64 for 64-bit Intel/AMD systems, arm64 for ARM64, or 386 for 32-bit x86. On macOS choose amd64 for Intel or arm64 for Apple Silicon. On Linux match x86-64 to amd64 or ARM64 to arm64 in the Release. Extract all files to a writable location. Avoid Chinese characters and spaces in the Windows path, move the extracted macOS executable at least once, and check Linux dependencies and execution permission.
The GUI and Mihomo core are managed separately. Open “Settings → Core”, check the “Mihomo” entry and choose “Update” if no local core exists. If it fails, inspect the download log and network. For manual installation, obtain the correct OS/architecture core from Mihomo’s official Release, name it for the chosen branch and place it in the mihomo subfolder of the actual data directory, then restart. Windows uses mihomo.exe or mihomo-alpha.exe; other systems need their own platform binary.
Open “Quick Start” in “Overview”, paste the complete compatible Mihomo/Clash subscription URL and save. Wait for the subscription and linked profile, select that profile, choose “Click to Start”, select a working node and enable “System Proxy”. Verify with a browser that honors the OS proxy. Basic use needs no extra manual profile. If no profile appears or startup fails, inspect download errors, the subscription response and core logs rather than repeatedly starting it.
Do not directly edit a generated profile controlled by a subscription. To add to or adjust the existing rules, find the current profile in “Profiles”, open “Edit → Mixin & Script” and save your changes under “Script”. For fully independent rule management, create a separate manually managed profile and save the rules in “Rules”. After saving, use “Generate and View” to check the rule order and proxy-group names, then update the subscription once to confirm your changes remain.
Starting the core does not set the OS proxy by default. Enable “System Proxy” in “Overview”, test a browser that honors it and inspect connection records. For TUN, first disable system proxy. On Windows enable “Run as admin” in “Settings” and approve the system permission request before testing TUN alone. Complete the core’s permission prompts on other systems too. If it still fails, check the active profile, selected group node and logs. If normal access also fails, disable the active capture path and check a normally direct site for recovery.
Find the active profile in “Profiles”, choose “Edit” and open “Proxy Groups”. Assign at least one subscription or node to every group, then save and regenerate. Remove circular references: if A includes B, B must not include A. If a subscription has no nodes, update it successfully before checking the group’s selections.
