Frequently asked questions

Start with your first connection if you are new. For network problems, follow the troubleshooting guide.

First confirm that you downloaded the app from the official releases, then download the package again in case it was incomplete. A “damaged” warning can have causes that are not fixed by removing the quarantine attribute; older xattr instructions are not a universal fix. If the warning persists, report the exact macOS and app versions in a GitHub issue.

For an unidentified developer warning, try to open the app once, then go to System Settings → Privacy & Security and choose Open Anyway for this app. See Apple’s instructions.

Archived and unsupported

The Clash Nyanpasu 1.6.x release line and all earlier versions have been fully archived and are no longer supported. They do not receive updates, fixes, or support.

Open Settings and use the folder buttons for the configuration or data directory. The tray menu also provides directory shortcuts. Logs are stored in the logs folder under the data directory. If the app cannot open, enter one of the platform paths below in your file manager.

• Windows: configuration under %APPDATA%/Clash Nyanpasu/config; data under %LOCALAPPDATA%/Clash Nyanpasu/data.
• macOS: ~/Library/Application Support/Clash Nyanpasu.
• Linux: configuration under $XDG_CONFIG_HOME/clash-nyanpasu or $HOME/.config/clash-nyanpasu; data under $XDG_DATA_HOME/clash-nyanpasu or $HOME/.local/share/clash-nyanpasu.

Since v1.6.0, configuration and data are stored separately; the log directory is inside the data directory. On Windows, the configuration directory can be customized or migrated. Custom directory settings take precedence over these defaults.

For the Windows portable package, the configuration and data directories are .config/clash-nyanpasu and .data/clash-nyanpasu beside the executable. See installation for package differences.

Open Settings → Nyanpasu Settings and change Application Log Level. The change takes effect as soon as it is saved. Available levels are trace, debug, info, warn, error, and silent (no application log output).

Older instructions that edit nyanpasu-config.yaml refer to the legacy settings file. For the current app, change the log level in Settings.

Follow System Proxy and TUN. The required steps depend on your platform and release package. Do not apply old manual permission commands from version 1.x to a 2.0 installation.

Some providers select the response based on the request’s User-Agent. By default, Clash Nyanpasu sends clash-nyanpasu/v{version}, where {version} is the app version. Ask your provider to allow this value, or change the profile’s User Agent to a value the provider accepts, such as clash-meta. You can set it while importing a subscription or edit it in the profile’s update options. Do not share your full subscription URL in a public issue.

The application/core directory contains bundled resources and core files. Open it from the tray menu or Settings. The app also provides system-service installation and management under Settings → System Service; follow that flow instead of manually installing service binaries. Most users do not need to edit files in the application directory.

Start with System Proxy and Rule mode. Use TUN when you need to include applications that do not follow the operating system’s proxy setting, and review its permission requirements first.

Open Settings → Clash Settings and use Core Manager. For the available engines and compatibility notes, see Choose and manage a core.

See Profiles and subscriptions to import or update a configuration, then Dashboard and traffic analysis to explore runtime data.