Overrides, groups and added rules
Illustrated steps
Choose an override mode
Open Override from the profile menu.
| Mode | Behavior |
|---|---|
| Merge | Keeps subscription groups/rules and layers personal settings; personal rules precede subscription rules, while existing added rules retain priority |
| Custom | You maintain groups and rules yourself |
Start with Merge. Empty custom content does not provide a usable routing configuration.
Route a website
- Add a personal rule in Override, or use Tools → Advanced Configuration → Added Rules.
- Choose a rule type such as domain suffix and enter
example.com. - Select Direct, Reject, an existing group or a Tailscale network.
- Save and apply while using Rule mode.
- Make a new connection and inspect its matched rule.
Domain fields do not take full page URLs. Old connections can survive a rule change, so reopen the destination when testing.
Groups and scripts
Create named groups with valid members before referencing them. Recheck rule targets after renaming or deleting a group.
Tools → Advanced Configuration → Scripts changes generated configuration; it is not an HTTP-response rewriting interface. Use trusted scripts, preserve a recovery copy and disable the script for comparison if something fails.
Direct edits to a downloaded subscription may disappear on sync. Keep lasting changes in the appropriate override controls.
For rule types and matching syntax, see the mihomo routing-rule reference. Use node or group names that exist in your active profile rather than copying example targets blindly.
Merge example: change one domain's outbound
First confirm a group named Work exists on the proxy page. In the selected profile's merge override, add the suffix example.com and choose Work as its target. Save and check the configuration, then test a destination in Rule mode.
If it does not match, check capture, Rule mode, higher-priority added rules, the existence of the target group and whether you tested an old connection, in that order. Remove the example rule and reapply to restore the subscription's handling of that domain.
Global added rules affect multiple profiles; personal rules in a profile override belong to that profile. Put an exception in the profile override when it should apply only to one subscription.
Process lookup and rule-driven detection
Check the switch and its explanation under Tools → General → Connection → Find process. The maintained version behaves as follows; check your version if an older build lacks the explanation.
| State | Behavior |
|---|---|
| Process lookup enabled | Actively looks up processes, with potential overhead |
| Disabled, but current rules need process information | Still looks up processes when checking those rules; the explanation says “Process rules look up the process only when they are checked” |
| Disabled and ordinary rules need no process information | Does not actively look up processes for ordinary rules; connection records may lack a process name |
A referenced classical rule provider that could contain process rules can also enable rule-driven detection. Turning off the switch does not prohibit all process identification. The desktop download-application Direct policy below is separate.
When diagnosing a process rule, first confirm that the application's traffic reaches the client. Save and apply the profile, then check the matched rule and outbound on a new connection. A missing process name alone does not prove a rule failed. Do not assume this device can identify processes on another device using its LAN proxy.
Desktop BitTorrent applications use Direct
The maintained Windows, macOS and Linux versions force recognized local BitTorrent applications, such as qBittorrent, Transmission, Deluge, aria2c and Motrix, to DIRECT. This policy precedes Rule and Global modes and cannot be disabled through subscriptions, personal rules or the process-lookup setting.
Those recognized connections use the local network's exit and can expose its public IP to peers. Check the process and outbound in connection records; Global mode alone does not establish that BitTorrent uses a proxy. This is not a guarantee of identifying all P2P traffic and does not describe Android or other devices connecting through a LAN proxy.
Script options and restore
Refresh script options manually when needed, check unsaved inputs, and review additions, changes and removals in the preview. Resolve missing-script or application errors before applying again.
Restored scripts need inspection and manual enabling. A successful profile restore does not mean its script is already affecting routing. See backup and restore.