Policy groups and proxy chains
For iPhone / iPad. Supported configuration can also sync to Apple TV.
Create and select a group
In Proxies → Policies, create a named group, choose its type and add members. Select the saved group on Home or as a rule target; creating it alone does not route traffic through it.
| Type | Use |
|---|---|
| URL test | Select using configured connectivity tests |
| Fallback | Prefer earlier members and switch when unavailable |
| Load balance | Distribute separate connections among available members |
| Smart | Learn from real connections and try another member when setup fails |
Auto Select is the built-in automatic group. Empty or unusable groups require checking member sources, filters and test results.
Tests and priority
Use a reachable test URL and keep the default interval initially. For Smart priority, lower values are preferred and 1.0 is neutral. Automatic changes normally affect new connections; reopen the target connection when checking a switch.
Why Auto Select latency may stay unchanged
In the maintained version, the built-in Auto Select skips a scheduled background retest if no proxied traffic has occurred since the previous check. An interval does not imply continuous idle testing. Network changes, failed connections or relevant configuration changes can still trigger a check. Do not generalize this behavior to every custom group or another client.
To compare nodes immediately, long-press one under Proxies → Servers and choose Test Latency. Use Test All in the toolbar for a batch, or a folder's menu to test its members. Tap an existing latency result to view details.
After testing finishes, check Auto Select's current choice on Home and create a new request to inspect the outbound. A low manual result does not guarantee automatic selection or service availability. An unchanged number alone is not a connection failure.
Proxy chains
- Add a chain in Proxies with at least two nodes.
- Arrange the entry and subsequent nodes in forwarding order.
- Select the chain on Home or in a rule.
- Verify the final exit and compare performance.
Test every member separately first. Longer chains are not inherently faster, and a failure in any segment can break the chain. Avoid circular dependencies.