Clash Verge Rev Guide

Hold the success bar in week one. Week two: learn Tun/rules/AI on demand; on shared PCs, agree who edits subscriptions.

Match arch before installing. Upgrade via backup → overwrite → accept; on day one watch boot restore and subscription updates before Tun.

Ignore vanity node counts. Confirm Clash Meta format and your regions; trial evening peak before annual billing.

Follow a week-one health schedule after import. On shared PCs, isolate subscriptions so nobody deletes another person’s primary link.

Compare the panel with the field checklist. After nodes appear, latency + system proxy accept; all-red goes to latency tests—not reinstall loops.

Check the panel before the client. Triage with the status-code card; rotate backup links by day—do not swap three times in one afternoon.

Tun fits CLI/AI; browsing-only can stay on system proxy. Watch CPU/sleep stability; do not assume containers are captured.

On Windows, install and accept Service Mode before blaming the airport when Tun won't stay up.

Verify toggle and ports, then Connections. Use a toggle contrast test; if only one browser fails, check extensions first.

Read the mode label and Connections hit line before flipping Rule / Global / Direct. Don't confuse dead nodes with the wrong mode.

When Telegram or a terminal proxy fails, check the live mixed port in Settings before blaming nodes.

Snapshot Merge before edits. After Rule/Global toggles, verify with Connections; prefer lean sets over mystery mega lists.

Keep Merge as small patches. After edits, verify hits in Connections. If rules do not apply, check mode, syntax, and priority before adding more lines.

Scripts are powerful and risky. Prefer Merge for static exceptions; keep scripts short, understood, and instantly disable-able.

Chains can stitch exits but double failure points. Prove each hop alone, then chain; segment-disable when unstable.

Steam downloads often should DIRECT. Patch via Merge, confirm in Connections, and never stack Tun with another game booster.

After DNS edits, watch 24 hours. Do not give every device a different DNS story; roll back the snapshot first when things break.

fake-ip speeds routing with synthetic addresses. If apps break, contrast redir-host and filter LAN domains before reinstalling.

Run the 10-minute control at peak hours. If tuning fails, swap nodes/providers—do not endlessly edit DNS and rules.

Match the check card, then open the article. After upgrade storms, restore backups first and fix subscription → nodes → capture in order.

A failed update check doesn't mean the client is dead. Compare version strings, then overlay a manual installer.

Offline after lid-close: check whether Connections shows rows. Most cases need a full relaunch or Tun toggle.

Copy subscription URLs and Merge before any reset. Reinstalling binaries often leaves a messy user config untouched.

If a group is empty, check total nodes first, then filters and group references. Empty group ≠ dead provider by default.

Kill leftover cores first, then AV/ports, then repair/reinstall the core. Do not blame “communication error” for all-red nodes.

Split UI vs core first. Stop aggressive testing/logging, check Tun and dual clients, then restart or upgrade.

When Connections has rows but pages fail, check rules/DNS/HTTPS inspection. IP works but domain fails → DNS first, not a client reinstall.

Identify the occupant first. After changing ports, sync system proxy/IDE/phone and write the new port down to prevent repeats.

Connections first, logs second. Capture only the repro time window and redact tokens; map keywords to articles before editing.

Locate the config directory first, then back up or reset. Subscription URLs and Merge matter more than copying mystery folders blindly.

WebDAV is great for snapshots, not your only backup. Test a manual upload before automation; keep subscription URLs elsewhere too.

Allow only trusted sources. On shared PCs, do not permanently exclude Downloads; watch 24 hours for AV re-quarantine after allowing.

Auto-start ≠ proxy written. Triage client → core → subscription → system proxy/Tun → network ready. AI/CLI still need Tun.

Offline after lid-close: check whether Connections shows rows. Most cases need a full relaunch or Tun toggle.

On Windows, install and accept Service Mode before blaming the airport when Tun won't stay up.

A working browser does not mean the terminal is proxied. Confirm the mixed port, set HTTP_PROXY or tool config — or use Tun when you run many AI CLIs.

WSL2 does not inherit Windows system proxy. Point HTTP_PROXY at the host IP:mixed port, or validate Tun carefully. Confirm Linux egress in Connections.

Download only from verifiable channels. Appeal false positives with hashes and release pages—never switch to mystery “AV-proof” packs.

Verify a trusted download, then remove quarantine. After it opens, accept via import → latency → system proxy—do not enable Tun first.

Trust Connections, not the tray icon. Match package format and permissions; you can toggle proxy from the window without a tray.

On travel, test both cellular and hotel Wi‑Fi. Agree on one subscription URL with desktop; whitelist background to avoid fake-online.

Match arch before installing. Upgrade via backup → overwrite → accept; on day one watch boot restore and subscription updates before Tun.

Keep subscription URLs in a password manager and Merge dated. Finish restore acceptance before retiring the old PC; do not leave tokenized links in public cloud roots.

Stop per-app proxy sprawl. Test a live node, enable Tun, verify each tool in Connections. Geo errors need new nodes; ignored system proxy is what Tun solves.

Harness decides how a model does work, not which weights you download. Separate those layers before you touch Clash Verge.

Want the UI first? Install Node, run one npx. If the download stalls, fix shell egress before cloning the monorepo.

Clone when you need plugins or mainline. Flow: clone → pnpm install → build → dsh web. Verify GitHub and registry egress separately.

A working API chat is not a working agent tool path. Make one outbound mini-task leave a Clash connection row before you tune anything else.

The Web UI binds to localhost and has no team login wall. Decide per-laptop vs one host + SSH tunnel before you share keys or workspaces.

A working browser session is not a working desktop app. Accept Claude.ai first, then Desktop; do not debug them as if they were Claude Code.

A working CLI is not a working VS Code extension. Accept ChatGPT web Codex, the VS Code extension, and Codex CLI as three layers.

After switching accounts, re-run one chat acceptance. Team workspaces may be stricter—pin a verified exit.

Accept with one chat in Connections. Region blocks with rows mean swap egress; Google Search working ≠ Gemini working.

Accept with one chat in a fresh terminal. After Claude Code upgrades, recheck Tun/env vars; do not keep a different port story from Cursor.

Unify ports when multiple Codex installs coexist. Under forced corporate PAC, use Tun or direct office domains while proxying model traffic.

Re-verify one completion after workspace trust changes. Direct or off-peak large index/npm traffic so it does not crowd model nodes.

After major IDE updates, re-run one completion acceptance. Separate timeouts from auth; do not twist corporate PAC and Clash together.

Pin a verified node before long jobs. If the repo hard-codes a proxy, switch it to env vars or Tun before moving machines.

Desktop Telegram/Discord often ignore system proxy. Fill 127.0.0.1:mixed-port or enable Tun; treat voice as a separate UDP/node check.

Prove proxy capture first, then use streaming-capable nodes with enough bandwidth. Low latency is not 4K capacity.

Treat Rev as the maintained client line. Subscriptions usually migrate; scripts/paths may need tweaks. Verify the Release, not the blog title.

Rev for maintained desktop GUI; Meta often means kernel ecosystem or Android apps. Reuse subscriptions; do not dual-run desktop GUIs.

Before uninstalling CFW, confirm boot restore and Tun on the new setup. Do not expect 100% plugin-path compatibility—trust Connections.

A/B the same subscription for cold start/Tun/updates/source. Review screenshots cannot replace your Connections page.

On migration day change only the GUI or only the provider—not both. Stop if the trial table fails.