Find supported clients and usage guides in one place, covering subscription imports, traffic routing, and TUN mode. Choose your device on the download page, then follow the guide to complete the first connection and verify traffic.
Each setting applies to a specific part of the network path. Understand the roles of the system proxy, TUN, rule mode, and DNS before changing switches; this makes problems easier to isolate than repeatedly changing nodes.
Importing a subscription is more than saving a URL. The client requests remote content, parses proxy nodes and proxy groups, and generates a selectable local profile. After pasting the URL, confirm that the request succeeds, select the newly imported profile, and check that its proxy groups appear. If the list is empty, first verify the URL, network permissions, and subscription service status instead of repeatedly adding the same address.
Clash Nyanpasu keeps profile management, update times, and enabled status together, making it easy to retain both a daily profile and a backup for troubleshooting. Before updating, note the current proxy-group choices; afterward, check whether group names changed so a new profile does not overwrite existing selections and get mistaken for a connection failure.
The system proxy mainly affects programs that actively read system proxy settings; some terminal commands, game launchers, and standalone network components may bypass it. TUN mode uses a virtual network interface to take over a broader range of traffic, which is useful when browsers work but terminal connections fail. Before enabling it, save any ongoing network tasks and check whether the system requires network-extension or administrator permissions.
TUN is not a universal fix. If the rules are wrong, DNS responses are abnormal, or the subscription has expired, taking over more traffic will not address the root cause. A safer order is to confirm that the profile starts, check the system proxy, then decide whether to enable TUN based on the application scope and retest the affected program afterward.
Rule mode matches requests against domains, IPs, processes, or rule sets in the configuration, then sends them to the specified proxy group. It suits everyday use because local services, directly accessed sites, and proxied requests can be handled separately. Global mode sends most requests through one proxy policy, making it useful for briefly testing node availability but not for judging whether routing rules are correct.
When troubleshooting routing, first inspect the matched rule, then see which proxy group it targets, and finally check the group's current selection. Changing a node in the proxy list cannot fix a request incorrectly sent to a direct-connection group. Clash Nyanpasu keeps rules and proxy-group controls separate; checking in the order of “request → rule → proxy group → node” is clearer.
DOMAIN-SUFFIXexample.orgProxyGEOIPLANDirectMATCHAll other requestsNode selectionDNS determines which address a domain resolves to first; rules determine which policy handles the subsequent connection. Check DNS separately when a site reports that the domain cannot be resolved, only some sites fail through the same node, or resolution remains broken after closing the client. Confirm that the client core is running, then compare system DNS results with those from the configured DNS to avoid mistaking resolution issues for poor node quality.
After changing DNS, account for system, browser, and client caches. Close old connections and send a fresh request during testing, refreshing the system DNS cache if needed. If enhanced mode is enabled, also verify the mode name, listening port, and conflicts with other local DNS tools. Narrowing the scope layer by layer is more effective than repeatedly replacing the entire configuration.
The homepage provides platform navigation only. On the download page, compare Clash Plus, Clash Verge Rev, FlClash, Clash Nyanpasu, and other clients for your platform, then choose a package based on your processor architecture and operating system.
Suitable for common desktops and laptops. Check your system architecture before installation. After installing, import the profile from the subscription page and enable the system proxy. If the core will not start, check security-software blocking, port conflicts, and configuration syntax.
Go to downloadsWhen downloading, distinguish Apple silicon from Intel processors. If a system security warning appears on first launch, confirm the app's permissions in System Settings. Enabling TUN may also require permission for a network extension; retest the connection afterward.
Go to downloadsSuitable for phones, tablets, and some TV devices. After installation, create a local VPN connection. Battery-saving policies may stop the client in the background, so check background permissions and battery-optimization settings for long-term use.
Go to downloadsOpen the Clash Plus installation page through the app store. On the first connection, the system will ask to add a VPN configuration; confirm it before importing the subscription. If access fails after changing networks, disconnect the old connection and establish a new local VPN session.
Go to downloadsProvides a graphical client and a Mihomo core entry point for servers and routers. Desktop users can start with the graphical interface; command-line deployments should first review service management, configuration paths, and file-permission requirements.
Go to downloadsChoosing a Clash client for long-term use requires more than evaluating its interface. It is more important to understand how the graphical client invokes the core, how configuration determines traffic paths, and how project updates reach the local installation.
Clash Nyanpasu is part of the Clash graphical-client ecosystem, handling profile imports, proxy-group selection, system-proxy control, TUN toggling, log viewing, and core management. The interface reduces the effort required to edit configuration files directly, but actual network behavior is still determined by the selected core and current configuration together. A “connected” status only means that the client process is running; it does not prove that the subscription, rules, DNS, and destination node are all working.
Treat the client as an entry point for managing configuration and the core. When troubleshooting, first confirm that the client has started, then inspect core logs and configuration loading results, followed by proxy-group and node connectivity. Layered troubleshooting prevents expired subscriptions, incorrect rules, or local port conflicts from all being blamed on the client itself.
Public code makes feature changes, issue reports, and fixes traceable in the project repository. Users can review commit history, release notes, and known issues, while maintainers can locate problems through reproducible logs and steps. When reporting an issue, include the operating system, installation method, current proxy mode, actions before and after the problem, and relevant processed log excerpts instead of an unreproducible statement such as “it doesn't work.”
Open-source collaboration does not mean every issue will be solved directly by the client. Subscription content comes from the relevant service, node status depends on the route, and system network permissions are managed by the operating system. Clearly separating these responsibilities helps send issues to the right place and reduces aimless switching between settings pages.
Mihomo reads configuration, establishes proxy connections, matches rules, handles DNS, and provides runtime status to the graphical client. Clash Nyanpasu organizes these capabilities into an operable interface. Concepts such as proxy groups, rule sets, mixed ports, TUN, and enhanced DNS modes originate in the core configuration; switches in the client usually translate into corresponding configuration values or startup parameters.
This is why the main routing results for the same configuration are usually similar across clients, while system-proxy integration, permission requests, tray controls, and update workflows may differ. When migrating clients, back up the subscription URL and custom configuration, then restore settings one by one rather than assuming that every switch name and default behavior is identical.
Clients, cores, and subscription profiles follow separate update cycles. A client update may change the interface or system integration, a core update may add configuration capabilities or alter compatibility, and a subscription update may change nodes, proxy groups, and rules. There is no need to update all three at once; a safer approach is to handle one layer at a time and verify startup, subscription, rules, and the target site after each change.
Before updating, record the active proxy group and key switches. Afterward, read the release notes and run a basic connectivity test. If something fails, preserve the old configuration and clear reproduction steps to help determine whether the cause is local settings, upstream configuration, or a new feature change. The site's download page organizes platform entry points, while the guides and troubleshooting pages cover initial setup and issue diagnosis respectively.
git clone https://github.com/LibNyanpasu/clash-nyanpasu.git
Most connection issues fall into six layers: client startup, configuration loading, system takeover, rule matching, DNS resolution, and node connectivity. Identify the layer first, then choose the corresponding fix.
First confirm that the subscription request succeeded and that the new profile has been selected. An incomplete URL, a temporarily unavailable subscription service, an incorrect system clock, or local security software blocking the request can all cause import failures. If the profile appears but the proxy list is empty, check the core logs for configuration-format errors. Read the subscription import steps in Getting Started, then visit the Glossary to understand the difference between subscriptions, profiles, and proxy groups.
The system proxy only affects programs that actively read system settings. Some terminal tools require proxy environment variables to be configured separately or need TUN mode to take over their traffic. Check the terminal tool's protocol and port first, then decide whether to configure environment variables or enable TUN. Do not change the system proxy, environment variables, and DNS in the same test, or it will be difficult to tell which setting took effect. See Troubleshooting for the complete process.
Rule mode uses domains, IPs, or rule sets to decide between direct and proxied connections, making it suitable for everyday use. Global mode sends most requests through one proxy policy and is useful for briefly testing node connectivity. If global mode works but rule mode fails, inspect the rule and proxy group matched by the request instead of staying in global mode. See the Glossary for MATCH, GEOIP, proxy groups, and related concepts.
Disable TUN first and confirm whether the basic system proxy works again. Then check administrator permissions, the virtual network interface, DNS configuration, and conflicts with other VPN software. Do not delete the entire configuration immediately; its contents may be fine. Once basic connectivity is restored, enable TUN alone and test again. If the logs report interface-creation failure or insufficient permissions, address the system-level issue first. See Troubleshooting for symptom-specific steps.
These articles break down the checking order for specific symptoms, focusing on what to observe, how to narrow the scope, and which settings should not be changed together.
Speed changes may come from node quality, route congestion, protocol overhead, traffic multipliers, routing rules, or local DNS. This article starts with repeatable tests to separate node issues from local configuration.
Read the full article →When the client cannot start the core, first check whether another program is using the mixed port. Then decide whether to stop the conflicting process or change the configuration, instead of repeatedly reinstalling and encountering the same error.
Read the full article →Browsers, terminals, and standalone network components read proxy settings differently. This article checks browser override settings and terminal environment variables separately, and explains when TUN is needed.
Read the full article →