First time with Clash Verge Rev isn’t about memorizing menus. You need five things in a row: the right build, a subscription that updates, a non-empty node list, a selected working node, and a system proxy that actually writes to the OS. Skip one step and everything feels “broken,” even when each piece looks fine in isolation.
Install from the download center or a verifiable GitHub Release—skip random “optimized” zips. Prove the browser path on day one; leave Tun for CLI/AI until day two so you can tell which toggle caused a failure.
What “working” means on day one
| Check | Pass looks like | Red flag |
|---|---|---|
| Build | App opens and stays running | SmartScreen/macOS “damaged” blocks launch |
| Subscription | Update succeeds, node list populated | Empty list or update error |
| Node | Selected node, latency test responds | All-red or -1 latency |
| System proxy | Connections shows new rows | Green toggle, empty Connections |
Five steps
- Install for your OS and keep the app running. Windows SmartScreen: install tips; macOS “damaged”: macOS; Linux packages: Linux.
- Get a Clash/Meta subscription URL (choose a provider). A marketing page in the browser is not the YAML feed the client needs.
- Paste, save, and update immediately (setup). Still empty: no nodes. If the card shows an error, treat it as update failed, not “empty list.”
- Latency-test and pick a stable node (latency). On day one, “opens the target site” beats chasing the lowest millisecond number.
- Enable system proxy; open a site that needs the proxy and confirm Connections shows hits. Green toggle with an empty Connections page → system proxy.
Four pages to learn
Profiles hold feeds; Proxies hold nodes/groups; Connections shows whether traffic entered the client and whether it was PROXY or DIRECT; Settings has system proxy, Tun, ports, Allow LAN. Logs: logs—reproduce once, then grab lines around that timestamp.
A common beginner trap is hammering Update on Profiles without ever checking Connections. “Working” means new connection rows for the host you just opened, not a green icon alone.
Day one vs day two
Day one: browser only—refresh OK, node selected, system proxy written, Connections populated. Day two: Tun for Cursor/Claude/Git (Tun & AI). Rules/DNS/DIRECT come after it works (routing, DNS, DIRECT). Turning everything on at once makes it hard to see whether a rule misfire or a dead node caused the break.
If you only browse the web, system proxy is enough; Tun is optional, not a status symbol.
Jump links for stuck points
- Update errors → update failed
- Green toggle, home IP → system proxy
- Some sites only → sites blocked
- Everything slow / all-red latency → slow speed, latency
- Index → common errors
Before asking for help, note OS and client version, whether update succeeded or errored, whether Connections shows rows, and which toggles you changed.
Week-one habits
Back up the subscription URL (backup). On shared PCs, agree who may toggle the proxy and watch plan quotas. OS install overview: install by OS.
If the browser is mostly stable with occasional single-site failures, swap nodes or check DNS before reinstalling. Reinstall when the profile directory is corrupt or the OS proxy never writes—not as the first reaction to one bad node.