Mode Overview
Rule Mode
Rule mode is the core Clash workflow. Instead of sending everything through proxy or direct, it matches each request by domain, IP, GeoIP, process, or custom rules, then routes it to DIRECT, PROXY, REJECT, or a policy group. For daily use, keep Rule mode as the baseline.
- Routing behaviorMatch requests by rules, then route to direct, proxy, reject, or a policy group.
- Common namesRule, Rule Mode, Rule-based.
- Best forDaily browsing, cross-border access, local direct traffic, precise routing.
Use Cases
When to use it
Daily default
Keep local and domestic traffic direct while proxying traffic that needs a node.
Multi-workflow routing
Different sites, regions, apps, and domains can hit different policy groups instead of sharing one route.
Account stability
Sensitive workflows can use fixed-region policies while regular services stay direct or automatic.
Setup
Setup advice
- Use trusted rule setsChoose actively maintained rules with clear categories to reduce false matches.
- Order rules carefullySpecific domain and business rules should appear before broad fallback rules.
- Inspect rule hitsWhen access fails, check connections or logs to see which rule and policy group matched.
Best Practice
Usage notes
Best practice: Rule mode should be the default. Switch to Proxy, Direct, or Manual only for troubleshooting, testing, or fixed-exit workflows.