Clash Verge Rev Interface Tour: Proxies, Profiles & Logs Tabs Explained

Interface Overview: The Sidebar Is Your Main Hub

When you first launch Clash Verge Rev, the window splits into a vertical sidebar on the left and a content area on the right. From top to bottom, the sidebar lists: Proxies, Profiles, Connections, Rules, Logs, Test, and Settings. The first five tabs each show a different slice of the kernel's runtime state, while Settings gathers client-level and system-level toggles in one place. The current kernel version and running status sit fixed at the bottom of the sidebar — check there first to confirm the kernel actually started.

One thing to understand up front: Clash Verge Rev is the GUI shell — the actual traffic routing is handled by the bundled mihomo kernel (formerly Clash Meta). Every toggle in the interface ultimately talks to the kernel through its external controller API. Once you get this relationship, it's much easier to place what each tab is for.

Proxies Tab: Picking Nodes and Switching Proxy Mode

The Proxies tab is the one you'll use most. It has two layers: a proxy mode switcher at the top, and the proxy group / node list below.

Three Proxy Modes

• Rule: Traffic is routed according to the rules in your config — matched traffic goes through the proxy, everything else goes direct. This is the mode used for nearly all everyday scenarios.
• Global: All traffic is sent through whichever node the Global proxy group points to. Use this when you need to force everything through the proxy temporarily.
• Direct: All traffic bypasses the proxy entirely. Handy for testing whether an issue is actually caused by the proxy.

Switching between the three modes takes effect immediately — no restart needed. The same switch is also available from the system tray menu.

Proxy Groups and Nodes

Each proxy group appears as a card, labeled with its type (manual select, auto speed test, etc.) and the currently selected node. For manual-select groups, just click a node name to switch. For url-test groups, the kernel picks the node automatically based on latency, and the card shows the current auto-selected result.

The lightning-bolt icon on a card triggers a latency test for the whole group, showing milliseconds under each node; nodes that time out or are unreachable are marked timeout. Latency here reflects connection time to the node, not actual download speed — treat it only as a reference for switching. Nodes are grouped by their source subscription; when the list gets long, use the filter box at the top of the tab to search by keyword.

Profiles Tab: Importing, Updating, and Switching Subscriptions

The Profiles tab manages complete profiles — each profile bundles nodes, rules, and proxy groups together, and usually maps to one subscription link.

Importing a Subscription

Click "New" to open the import dialog. There are two options: Remote, where you paste a subscription URL and the client fetches and saves the content; and Local, where you pick an existing YAML file. Remote profiles support an auto-update interval in minutes — set it to 0 to disable auto-updating.

Actions on a Profile Card

Each profile shows up as a card with its name and last-updated time; if the subscription provider supplies usage data, traffic stats show up too. Common actions from the card menu:

• Update: Re-fetch the subscription content right away — use this after the provider changes nodes or rules.
• Edit Info: Change the display name, subscription URL, or auto-update interval.
• Edit File: Edit the YAML directly in the built-in editor; changes take effect automatically on save.
• Open File: Open the profile's folder in your system's file manager.

The currently active profile is highlighted. Clicking another card switches the whole set — nodes, rules, and proxy groups all change together, no client restart required.

Global Merge & Script Overrides

The "Global Merge & Script" section in the upper-right of the Profiles tab offers two entry points — Merge (YAML merge) and Script (JavaScript) — for overriding or appending fields without touching the original subscription content, such as globally changing DNS settings or adding custom rules. When a subscription updates, its original content gets overwritten, but these overrides stay untouched — ideal for storing long-term personal tweaks.

Connections and Rules Tabs: Seeing Where Traffic Actually Goes

Connections Tab

The Connections tab lists every active connection line by line: the source process, source address, destination address and port, the matched rule chain, live upload/download speed, and cumulative traffic. Any single connection can be closed individually, and there's a one-click button to close all connections at once.

To check whether a specific app is actually going through the proxy, open the app, trigger a request, and watch for the new row on the Connections tab — the rule chain shows exactly which rule matched and which node the traffic exited through.

Rules Tab

The Rules tab lists every rule in the current profile in order, along with each rule's cumulative hit count. Clash matches from top to bottom, stopping at the first hit — so the order shown here is the priority order. If a custom rule isn't taking effect, check here first to see where it sits and whether a rule higher up is intercepting traffic first.

Logs Tab: Your First Stop for Troubleshooting

The Logs tab streams the kernel's runtime output in real time. Three controls sit at the top: a log level dropdown, a search box, and pause/clear buttons. What each level means:

• error: Errors only — check this level for startup failures or subscription parsing errors.
• warning: Warnings and above.
• info: The default level, including connection establishment and rule match records.
• debug: The most verbose level, printing the full rule-matching process.
• silent: Disables log output entirely.

A typical info-level line looks like this — each row includes a timestamp, log level, and a connection record, ending with the matched rule and exit node:

time="2026-07-28T10:21:03+08:00" level=info msg="[TCP] 198.18.0.1:51234 --> www.example.com:443 match DomainSuffix(example.com) using Auto/HK-01"
time="2026-07-28T10:21:09+08:00" level=info msg="[TCP] 198.18.0.1:51236 --> api.example.net:443 match Match() using DIRECT"

If a rule isn't taking effect, switch the level to debug, reproduce the issue, then filter the search box by domain — the matching process shows up line by line.

Settings Tab: System Proxy and TUN Mode

Clash Settings

The mixed port (default 7897), Allow LAN, IPv6 toggle, and the external controller address and secret all live here. If you change the port, remember to update it in any app where you manually entered the proxy address.

System Settings

• System Proxy: When enabled, this writes the proxy settings into the OS automatically — browsers and most desktop apps pick it up right away. This is the main switch most people use.
• TUN Mode: Takes over all traffic at the kernel level, catching apps that ignore the system proxy setting (some games, CLI tools). Before enabling it for the first time, you'll need to install the service mode — there's an install button right next to the toggle, and the toggle only becomes usable once that's done.
• Everything else: launch on startup, silent start (skip showing the main window on launch), and tray icon behavior; the Appearance section covers light/dark theme and interface language.

Each of the six tabs handles its own piece: Proxies for routing, Profiles for subscriptions, Connections and Rules for tracing traffic, Logs for troubleshooting, and Settings for toggles. Once you're comfortable with the layout, follow the setup guide to import a subscription and turn on the system proxy — and you're ready for everyday use.