Profiles and subscriptions
A profile supplies the Clash-compatible configuration that Clash Nyanpasu prepares for the selected core. The app natively supports multiple cores, and each core can differ in the fields and extensions it accepts.
Choose a profile source 3 source types
Section titled “Choose a profile source ”Use a remote profile when your provider gives you a subscription URL. Clash Nyanpasu downloads and stores the profile, and can refresh it manually or on a schedule. The provider may also return usage and expiry information.
The import form has optional user-agent, connection, and update-interval settings. Leave the interval empty to use a provider-suggested value when available; otherwise the app uses its 120-minute default.
Use a local profile when you have a .yaml or .yml configuration file. Importing it copies the file content into the app-managed profile. Changes you later make to the original file are not synced automatically.
Use a linked file when another app or editor owns the source file and you want Nyanpasu to follow it. Choose Mirror to keep an app-side copy synchronized with the source, or Symlink to reference the source path directly.
If you do not have a profile or subscription yet, contact your provider; Clash Nyanpasu does not provide proxy subscriptions.
Import a profile
Section titled “Import a profile”- Open Profiles and choose Profile in its sidebar.
- Select New config, then choose Single.
- Choose Remote, Local, or Linked file and provide the URL or file path described above.
- Set a name and optional update interval, then choose Submit.
- Select the new profile and use Activate Profile if it is not already active.
For the complete first-run flow, see Make your first connection.
Update a subscription Remote profiles
Section titled “Update a subscription ”- Open the remote profile’s details and choose Update to fetch its current URL.
- Choose Update Opts to enable or disable Auto Update and set the interval in minutes.
- Check the profile’s Updated time after a refresh. A configured interval is only a schedule; it does not confirm that a refresh succeeded.
Leaving the update interval empty uses the 120-minute default in the update-options editor. Changing the subscription URL and saving it triggers an immediate fetch from the new URL. Updating a profile does not renew or extend the provider’s subscription.
If an update fails, check that the URL is current, the provider allows requests from this app, and the configured user agent or connection options match the provider’s instructions. Do not share the URL when asking for help; the troubleshooting guide explains what information is safe to provide.
Profiles and transformations
Section titled “Profiles and transformations”The profile is the input; a transformation changes that input while the app builds the runtime configuration. Keeping your own transformations separate from a provider’s remote profile makes subscription updates easier to review. See Profile transformations for the 2.0 workflow and inspection tools.
After switching cores, check the profile and transformation fields against the newly selected core. A field accepted by one core may be unsupported or behave differently in another; see Choose and manage a core.
If the core starts but traffic does not use the expected profile, confirm which profile is active, then review the selected proxy group and proxy mode.