Who this guide is for—and what it skips

This article assumes you already downloaded Clash Verge Rev, granted macOS permissions prompted by the tray helper, and imported at least one subscription or local YAML profile that loads without parser errors. If you still need a zero-to-first-byte installation narrative focused on another desktop OS, start with the ecosystem onboarding pieces first; here we stay inside the macOS tray workflow where everyday operators spend ninety percent of their time.

Readers arrive with questions such as how to use Clash Verge Rev on macOS, what rule mode actually changes compared with global mode, whether TUN is mandatory, and where policy groups hide inside nested selectors. We translate those UI labels into engine behavior so you stop guessing which toggle fixes Safari while Terminal stubbornly goes direct.

Deep dives on bespoke YAML, remote rule providers, or Git-backed rollback live elsewhere—yet every recommendation below still respects your profile because Verge is fundamentally a shell around a Mihomo-class core executing standard rules and proxies sections.

Mental model: modes, listeners, and policy groups

Think in three stacked layers. At the bottom, individual outbounds represent concrete servers—Shadowsocks, VMess, VLESS, Trojan, or even SOCKS hooks—each with latency and cipher knobs. Above them sit policy groups (the YAML proxy-groups list) that bundle outbounds under strategies such as Selector for manual picks or URL-TEST for automated probes. Finally, modes tell the core how aggressively to consult your rule chain before falling back to broad defaults.

Rule mode is the precision instrument: every new flow walks your ordered rules until one matches, then hands execution to whichever outbound or nested group that rule names. Global mode compresses that story—eligible streams jump into the configured global proxy pile so you can verify connectivity quickly without mentally simulating DOMAIN keywords. Direct mode bypasses most redirection useful when isolating whether slowdowns originate from upstream nodes or local DNS drama.

Neither mode magically fixes malformed subscriptions; they only decide how aggressively rules engage once packets reach the daemon.

System proxy versus TUN on macOS

Apple exposes a system-wide HTTP and HTTPS proxy preference that well-behaved GUI apps honor automatically. When Clash Verge Rev enables system proxy, it typically programs those fields to point at the local mixed listener alongside optional SOCKS references depending on your profile. That path is lightweight, plays nicely with selective exclusions, and mirrors how corporate laptops expect proxies to behave.

The trade-off is visibility: anything that spawns raw sockets without consulting CFNetwork proxy dictionaries—common with Homebrew-built CLI utilities, bespoke Go binaries, or games using proprietary transports—may ignore those settings entirely. That gap fuels endless Reddit threads claiming “Clash works in Chrome but not ping.”

TUN mode addresses bypass by inserting a virtual network interface and steering traffic at the IP layer subject to OS routing tables and Mihomo’s tunnel logic. After macOS approves the privileged helper, far more processes ride through the stack you configured, which is why advanced tutorials pair TUN discussion with DNS modes and fake-ip caveats. Because both layers interact, toggling TUN without revisiting DNS can produce confusing split-brain resolutions documented in our TUN deep dive.

Running another kernel-extension VPN simultaneously may reorder interfaces; pause conflicting clients before blaming Verge for loops or upload stalls.

Step 1—Confirm the profile, ports, and logs

Before flipping modes, open your active profile summary inside Verge and confirm three realities: parser status is clean, nodes enumerate under the Proxies tab, and the log pane is not spamming TLS handshake failures against every outbound. If imports fail, fix YAML first—modes cannot compensate for expired subscriptions or mismatched cipher suites.

Note the mixed HTTP/SOCKS port numbers your bundle advertises; you will reuse them when syncing Terminal environments per our macOS shell proxy guide. Writing ports on a sticky note beats guessing later when debugging partial captures.

Step 2—Choose Rule, Global, or Direct deliberately

Vacation troubleshooting often begins with Global mode because it removes ambiguity: either almost everything rides the chosen chain or nothing does, exposing upstream outages fast. Daily driving belongs in Rule mode so domestic CDNs stay local while foreign SaaS APIs traverse optimized exits—precisely the workload Clash-style engines excel at compared with blunt always-on VPN tunnels.

Switch to Direct mode when validating ISP issues, captive portals, or suspicious latency inflation introduced by a freshly imported remote rule set. Direct acts like a circuit breaker proving whether slowdowns persist without touching proxy hops.

  1. Anchor baseline measurements
    Capture speed tests or traceroutes in Direct mode so comparisons remain honest after enabling proxies.
  2. Promote Global temporarily
    When diagnosing handshake failures, Global proves whether any remote node works before you dissect DOMAIN-SUFFIX ordering.
  3. Return to Rule for routine use
    Reinstate split routing once health checks pass so streaming, banking, and videoconferencing each land on sensible paths.

Step 3—Enable macOS system proxy from Verge

Locate the tray menu entry governing system proxy integration—wording shifts slightly across builds but consistently mirrors macOS Network preferences. Activating it should populate HTTP and HTTPS proxy hosts with loopback addresses referencing your mixed listener unless your profile remaps ports.

Validate through Safari or another native browser first; they inherit system settings immediately. Then spot-check System Settings › Network › Details › Proxies to confirm no stale manual entries fight Verge. Conflicting legacy PAC scripts left from corporate laptops are a frequent invisible adversary.

Step 4—Turn on TUN when proxies feel “ignored”

Escalate to TUN once you confirm specific binaries Route Around system proxies. macOS prompts for administrator authorization because installing tunnel interfaces touches privileged APIs; approve promptly but read the dialog—users who reflexively deny helpers spend hours chasing phantom bugs.

  1. Shut down overlapping VPNs
    Disconnect IPSec or WireGuard clients that might reclaim default routes before enabling Verge TUN.
  2. Enable TUN inside Verge
    Toggle the service-style switch, wait for interface creation, then revisit logs for adapter errors or permission retries.
  3. Reconcile DNS modes
    Align Mihomo DNS stanza expectations with macOS resolver behavior so queries do not leapfrog the tunnel unintentionally.
TUN broadens coverage—and blast radius. Pair it with disciplined logging and avoid exposing REST dashboards without reviewing our localhost-only controller hardening guide.

Policy groups in the Proxies screen

In YAML, proxy-groups define policy groups; Verge renders them as expandable rows mixing emoji-heavy subscription branding with sober latency integers. A Selector group waits for your manual choice—ideal for picking regional exits or specialty chains reserved for banking sites. A URL-TEST group probes lightweight URLs on an interval, reordering children so the fastest surviving server rises to the top without micromanagement.

Nesting matters: rules often point to a group named PROXY or ♻️ Automatic rather than raw servers, letting operators swap upstream bundles inside the subscription without rewriting hundreds of DOMAIN lines. When documentation mentions “choosing a policy,” it usually means selecting which nested group satisfies the MATCH rule—not obsessively clicking leaf nodes unless troubleshooting.

Practice flow: expand the outer domestic versus overseas split if your provider ships one, select a concrete server inside the overseas Selector, then reload a targeted web app while watching connection logs to verify the chain updates instantly.

Switching nodes without surprises

Rapid node hopping is safe when you understand session stickiness. Long-lived HTTP/2 channels may linger until browsers reopen sockets; streaming stacks sometimes cache egress IPs per segment. After changing nodes, close stubborn tabs or pause playback briefly rather than assuming the engine ignored you.

For automation-friendly setups, prefer letting URL-TEST groups converge instead of hammering manual switches every minute—constant churn stresses subscription backends and skews latency metrics.

DNS, rules, and where Global still misleads newcomers

Beginners often conflate global mode with “everything exits remotely.” In reality, DNS resolution paths, IPv6 preference, and leftover DIRECT exceptions still sculpt outcomes. If QUERY logs show domestic resolvers while browsing feels foreign, pause and map DNS mode settings alongside rule traces.

Readers planning heavier customization should graduate toward structured rule authoring showcased in beginner routing tutorials; this article intentionally stays inside GUI toggles you can rehearse in minutes.

Troubleshooting snapshots

Symptom: browsers proxy, CLI tools do not

Export proxy variables mirroring local ports or enable TUN; partial setups confuse newcomers who expect one checkbox to retrofit every POSIX binary overnight.

Symptom: URL-TEST flickers between nodes

Narrow probe URLs, extend intervals, or remove unstable transports from the candidate pool—micro outages masquerade as flutter when probes are hyper-aggressive.

Symptom: hotel Wi-Fi breaks after enabling TUN

Disable TUN temporarily, finish captive portal authentication in Direct mode, then re-enable once the hotspot grants general routing.

Frequently asked questions

Is Rule mode slower than Global?

Rule evaluation adds trivial CPU overhead versus traversing a uniform proxy group; perceived slowdowns usually trace to DNS, QUIC blocking, or congested servers—not the matcher itself.

Must I always enable TUN on macOS?

No—prefer system proxy until evidence shows ignored processes. TUN trades convenience for breadth and deserves deliberate DNS pairing.

Are policy groups the same as subscriptions?

Subscriptions supply raw nodes; policy groups organize those nodes into selectable strategies referenced by rules. You interact with both layers but for different purposes.

Why nuanced clients matter—and where Clash fits

Many turnkey tunnel apps emphasize a single oversized connect button—they obscure whether traffic follows split routes, which DNS resolver answered, or why only some apps respected the VPN profile. Traditional all-or-nothing VPN silos solve café Wi-Fi quickly yet struggle when developers need domestic APIs and overseas repositories during the same compile loop.

Clash-class stacks restore transparency: explicit rule mode contracts, composable policy groups, optional TUN depth, and plaintext YAML you can diff like infrastructure. That combination answers macOS Clash tutorial seekers who outgrew opaque switches yet still want guardrails.

If you want to standardize client sources before layering exotic routing, open our Clash download page for curated builds per platform.

→ Download Clash and pair fresh binaries with the modes you practiced above

Visit our download page for Clash clients