Clash Verge Rev hotkeys: setup and conflict checks

Choose the window action, not a proxy toggle

When Clash Verge Rev is running in the background, a hotkey saves you from finding its tray icon every time you want to inspect a connection. The important first choice is the action: Open/Close Dashboard is separate from Enable/Disable System Proxy.

This guide targets an already installed Clash Verge Rev v2.5.2 on Windows 10/11, x64 or ARM64. Labels were checked against that release’s English interface. The project is maintained and is not the discontinued Clash for Windows. We will only control the window, leaving subscriptions, nodes, TUN and proxy modes unchanged. No patch or additional download is required.

Open Settings → Verge Basic Setting → Hotkey Setting. The example assumes that Open/Close Dashboard is currently unassigned. If it already has a combination, record it before making any change. Also note the current state of Enable Global Hotkey.

Record the keys, then click Save

The input records physical key presses; it is not a text field for typing the name of a shortcut. We use Ctrl + Alt + K as an example only. It is neither a built-in default nor a promise that the combination is free on your machine.

Check the other actions first. Do not assign the same combination to two actions.
Click the input beside Open/Close Dashboard. Hold Ctrl and Alt, press K, then release every key.
Check the displayed combination. Do not press Enter inside the recording field to confirm it: that can record Enter instead.
Enable Enable Global Hotkey if you need the shortcut while another application has focus. Click Save with the mouse and check for errors.

The global switch applies to the whole set: existing system-proxy, TUN or mode-switching bindings will also gain a different activation scope. If you do not understand those existing assignments, cancel the edit before enabling background shortcuts for all of them.

Test once with the window minimized

After a save without errors, reopen Hotkey Setting and confirm that the combination and global switch were retained. Close the dialog, minimize the main window using its minimize button, and focus another ordinary application. Press and release the new combination once, then check whether the dashboard appears.

The action toggles visibility; it does not always bring the window to the front. In v2.5.2 a visible window follows the hide path even when it is unfocused. A hidden or minimized window follows the show-and-activate path. Start from a known state and avoid pressing twice in quick succession, which can obscure what actually happened.

Global off does not mean deleted: this version limits execution to a visible, focused main window when the switch is off. It does not remove the binding or necessarily release its registration. To invoke the dashboard from another app, check the switch; to remove the combination, delete its assignment and save.

Verge must still be running. Its own registered hotkey cannot launch the application after you have exited it completely. That is a different feature from a launch shortcut assigned to a Windows shortcut file.

Match the check to the symptom

Symptom	Check first	Next step
The recorded keys are wrong	Input focus and the complete key sequence	Record once more, release the keys and inspect the result
Saving returns an error	The actual error, duplicate assignments and other software	Try a non-conflicting combination, not a different proxy node
It works only while Verge has focus	Whether Enable Global Hotkey was saved as on	Check the switch and other uses of the combination
The window disappears after a press	Whether it was already visible	Minimize it first, then make one test press

Input methods, screenshot tools, launchers and editors may use shortcuts, but an unresponsive key alone does not identify the owner. Inspect their settings and change one combination at a time. There is no reason to disable security software, reset networking or import the subscription again for this test.

Registration errors are returned to the interface, with wording determined by the operating system and underlying failure. Do not expect the dialog to reliably name a competing process. A successfully registered global shortcut can still interfere with a normal in-app shortcut, so test your everyday applications too. After a failed save, retain the error and check existing bindings again: do not assume that every previous registration was automatically restored.

Remove just this assignment when you are done

Return to Hotkey Setting and click the trash icon beside Open/Close Dashboard. Confirm that its key display is empty.
If this exercise changed the global switch and you have not added another use for it, restore its recorded state.
Click Save, check for errors, then reopen the dialog to confirm the empty assignment.
Minimize the dashboard and try the old combination while another ordinary app is focused. It should no longer trigger the dashboard; check your other existing bindings as well.

The trash icon edits the pending value, so saving is still required. You can cancel a new recording before attempting to save it. Once a save has failed, however, Cancel is not a guarantee that all runtime registrations have rolled back. If the action previously had a shortcut, restore the recorded original rather than clearing every hotkey.

One clear, tested window shortcut is enough for this task. Add other actions separately only when you understand what each one changes.

Official sources and version scope

Version numbers, filenames, and interface labels can change. Confirm them in the linked project documentation before making changes.