Lightweight mode closes the interface, not the proxy
Clash Verge Rev’s lightweight mode releases the main window and its WebView. It is not simply minimizing the window to the taskbar, and it does not change Rule mode to Direct. Use it when your configuration is already working and you do not need to keep the graphical interface open. The tray and background app remain; entering this mode does not issue a command to stop the Mihomo core.
This guide covers the maintained Clash Verge Rev v2.5.8 stable release on Windows 11, for x64 / ARM64, using the English interface. The procedure was checked against fixed-version source code, frontend and backend commands, and the five-language interface dictionaries. It was not verified by clicking through the Windows application. Do not apply the menus from the original Clash Verge, Clash for Windows, or another client.
The app must already open normally, and you must be able to find its icon in the Windows tray. Confirm that the current profile and proxy work before closing the interface. Lightweight mode will not repair an invalid node, nor does it guarantee a particular percentage of memory savings or faster connections. You do not need to install a service, reset a profile, or edit YAML to enter it.
Enter lightweight mode manually from Settings
- Open Settings in the main window. Keep the current subscription, proxy mode, and system proxy / TUN state unchanged; do not adjust network settings at the same time.
- Under Verge Advanced Setting, click LightWeight Mode Settings. This opens a dialog; it is not a proxy-routing mode.
- Find Enter LightWeight Mode Now and click Enable on the right of that row. For this manual action, leave the automatic-entry switch and delay below it unchanged.
- Wait for the main window to close, then right-click the tray icon and confirm that Lightweight Mode is checked. The window disappearing is expected; that alone does not prove the proxy is working or that the app has exited completely.
Enable sends the entry command immediately. You do not need to click Save at the bottom of the dialog. Save applies the automatic-entry switch and delay; these are different actions. If you accidentally changed those settings but have not saved, cancel the dialog first, then repeat the manual procedure above.
Leave lightweight mode and restore the main window
Right-click the Clash Verge Rev icon in the Windows tray and choose Dashboard. While the app is in lightweight mode, this action first leaves that mode, then recreates and shows the main window. Do not look for a separate menu item called “Open window”: the actual label in this version is Dashboard.
Alternatively, click the checked Lightweight Mode item to clear the current lightweight state and restore the window. Use one method, wait for the interface to return, and then check it; repeated clicks or a core restart are unnecessary. The tray’s left-click action is customizable, so a single click on the icon does not necessarily do the same thing for every user. The right-click menu gives a clearer match to this procedure.
Once the window returns, confirm that you can view the proxy page or logs. Use a page that previously worked to check that the connection is still available. Restoring the interface does not prove that every node, DNS lookup, or website is healthy, and you do not need to reimport the subscription for this action. This guide does not promise that a manually selected lightweight state survives an app restart; entering it once is not a saved startup preference.
How are hiding, lightweight mode, and Exit different?
| Action | Behavior in v2.5.8 | How to return |
|---|---|---|
| Click the window’s normal close button | The app intercepts the close request and hides the main window; with automatic lightweight entry disabled, this does not immediately release the window | Choose Dashboard from the tray to show the window |
| Enter lightweight mode manually | Releases the graphical main window while keeping the background app; it is not a command to stop the core | Choose Dashboard, or uncheck Lightweight Mode in the tray |
| Choose Exit from the tray | Runs the app’s exit procedure, including an attempt to stop the core; this is not lightweight mode | After a successful exit, start the app again |
If you previously enabled Auto Enter LightWeight Mode, closing the window starts a timer, and the app enters lightweight mode after the configured delay. The initial defaults in this version are automatic entry off and a delay of 10 minutes; an existing configuration may differ. This does not mean that an open window is closed every ten minutes.
Changes to automatic entry and its delay are submitted only when you click Save. Cancelling or closing the dialog does not save those edits. If you want future window-close actions to use ordinary hiding, restore the window, return to the same dialog, disable automatic entry, and save. The current lightweight state and this automatic preference are separate: unchecking the current state does not permanently disable automatic entry, and disabling automatic entry does not replace restoring the window from the tray.
If the window does not return, check the tray state first
Do not use Exit to leave lightweight mode. To keep the proxy running and restore the interface, choose Dashboard or uncheck Lightweight Mode. Exit attempts to stop the core. If a stop-failure message appears, keep the original information; clicking Exit alone does not establish that the background app has ended.
First confirm that the tray icon belongs to the running Clash Verge Rev app, check whether Lightweight Mode is selected, and use Dashboard to restore the interface. If the menu opens but the main window still does not appear, record the actual app version, Windows version, interface language, action sequence, and error message for the official project to investigate. Do not delete the configuration directory or install an unfamiliar patch just because the window is invisible.
A missing tray icon does not establish that the app is still in lightweight mode. First distinguish between an icon hidden in the notification area, an app that has successfully exited, and a failed startup. This guide does not attribute every missing-window problem to this feature. To use the graphical interface again, restore it from the tray; this manual entry does not require resetting the existing subscription or proxy configuration.
Official sources and version scope
- Clash Verge Rev v2.5.8 release
- Pinned source: advanced settings entry
- Pinned source: immediate entry and preference saving
- Pinned source: lightweight entry command
- Pinned source: lightweight state, restoration and timer
- Pinned source: tray actions and checked state
- Pinned source: window creation and destruction
- Pinned source: window-close and application-exit events
- Pinned source: exit cleanup and failure boundaries
- Pinned dictionary: settings labels
- Pinned dictionary: tray labels
Version numbers, filenames, and interface labels can change. Confirm them in the linked project documentation before making changes.