Rule set subscriptions

Open Routing rules → Rule set subscriptions to bind an entire domain/IP category to one outbound. Use manual rules for individual apps and exceptions.

TUN mode only

Downloaded or enabled does not mean a subscription is being used in System Proxy mode. Check the mode and restart requirements before verification.

Subscriptions, priorities, and downloaded entriesReal HypoMux 2.7.0 Chinese interface. The displayed Steam subscription and Direct outbound are local examples, not defaults or recommendations.

Add and verify

1. Enter a recognizable name, public HTTPS source URL, outbound, and priority from 0–999. Use a trusted rule maintainer.
2. Add the list and inspect status. Select Update now when needed and confirm successful download and parsing.
3. Open View contents and search for a domain/IP. Inspect actual entries and the ignored count; a successful fetch does not mean every source rule is supported.
4. Restart TUN when prompted, create new connections, and verify their outbounds.

The screenshot's Steam-to-Direct choice is only an example. Choose aggregation if that is your goal, and check higher-priority manual exceptions.

Supported formats

Supported domain/IP conditions can be read from Clash payload YAML and sing-box source JSON. This is not an import of complete proxy configurations, node subscriptions, or arbitrary binary rule packages.

Content types include exact domains, suffixes, keywords, regular expressions, and IP/CIDR. Inverted conditions, port conditions, and unsupported logical nesting cause the whole external rule to be ignored and counted, rather than silently dropping conditions and changing meaning.

Fetching requires public HTTPS and limits redirects, size, and duration. Local/private network sources are rejected. Use a raw rule file, not a repository HTML page or sign-in page, and inspect errors on failure.

Priorities and exceptions

Higher numbers rank earlier. Manual rules, match types, and more specific conditions also influence results. A subscription does not automatically override every manual rule. Give intended exceptions an explicit higher priority and test fresh connections instead of maximizing every overlapping list.

Reload or restart?

Change	Behavior
Contents or priority of a loaded list	Hot reload; verify new connections
Disable or delete	Hot reload; existing connections do not migrate
Add a list or change its outbound	Restart TUN
Enable a list not loaded in the current session	Restart TUN

Disable before deleting when diagnosing. On update failure, preserve the error and do not mistake cached counts for a successful new update. Manual-rule JSON backups are not complete application backups; do not assume they include subscription configuration and caches.

Common issues

• Fewer entries than upstream: Check ignored entries, deduplication, and unsupported source conditions.
• Updated but outbound unchanged: Verify TUN, any required restart, fresh connections, manual exceptions, and priority.
• Pinned adapter unavailable: Restore it or rebind to an available outbound and restart when prompted; do not guess adapter IDs.
• Configuration conflict: Another page or AI may have just changed rules. Reload current state instead of overwriting newer settings.

See manual routing, connections, and troubleshooting.