ClashX Official Site · Clash Client
Downloads & Setup

Rules are checked from top to bottom, and the first match determines the outbound policy. This example sends specified domains direct, then routes based on the destination region, with MATCH handling everything else. PROXY is not a built-in catch-all; it must refer to a node or proxy group in your configuration. After importing a subscription, select rule mode and enable connection logging to check the matched rule and actual exit. If one site has a problem, check rule order, domain resolution, and DNS results first rather than switching the entire configuration to global mode.

Importing a subscription downloads the provider's configuration to your client. The URL often contains access credentials, so keep it private. Copy the full URL, add it as a remote configuration in the client, and select it after the download completes so the core loads it. A local YAML file is a snapshot and won't update when the provider changes its configuration. A Base64-encoded list of proxy nodes may not work as a complete configuration. If an update fails, check the response status and content type, then make sure the URL hasn't expired. For format conversion, prefer a trusted local tool and avoid sharing your subscription with unknown services.

The system proxy changes the operating system's proxy settings. It's a good fit for browsers and apps that honor those settings, but it won't route every program. TUN captures traffic through a virtual network interface and can cover more apps, but also involves routing, DNS, and system permissions. For a first-time setup, test the system proxy before deciding whether you need TUN. Avoid changing multiple variables at once. When switching modes, check for other VPN or proxy apps and watch for routing conflicts with local networks, virtual machines, or corporate networks. Neither entry point determines the routing mode: once traffic reaches the core, the active configuration still chooses its route.

mihomo is a proxy core in the Clash ecosystem. It reads configuration, handles DNS resolution, matches rules, and establishes outbound connections. A graphical client adds subscription management, mode switching, tray menus, and permission services around the core. Similar client names don't guarantee the same core or supported configuration fields. Before following documentation, check which core your client actually uses and whether it supports the option in question. Client and core updates may also ship separately. If configuration parsing fails, check the specific field and error line rather than judging compatibility by the interface alone.

The menu bar or system tray puts common actions close at hand: switch configurations, choose an outbound mode, enable the system proxy, and open logs. Closing a window usually just hides it; it may not stop the core. Check the menu bar icon and client status to see if it's still running. When troubleshooting, verify the active configuration and mode before reviewing connection logs. Before quitting, consider disabling the system proxy set by the client and confirm that the system no longer points to a port that's no longer listening. Menus and quit behavior vary by client, so don't assume the steps for one app apply across platforms.