Many people think Clash Verge Rev is the whole thing, but it's only a graphical interface (GUI). The component that actually connects to nodes, parses protocols and forwards traffic is the underlying Mihomo core (formerly Clash Meta). v2.5.0 upgraded that core to v1.19.25.
How the core and client relate
Think of Clash Verge Rev as the "steering wheel and dashboard", and the Mihomo core as the "engine". Importing a subscription, switching nodes, enabling Tun — everything you click ends up handed off to the core. So the core version directly determines which protocols are supported and how stable it runs.
What the core upgrade brings
- Protocol compatibility: Mihomo keeps up with newer protocols like VLESS, Hysteria2 and TUIC, so a newer core works better with newer provider configs.
- Stability fixes: Core point releases usually include connection-handling and resource-cleanup fixes — better for people who leave it running for long stretches.
- Rule engine: Routing-rule matching is the core's job too, and core updates sometimes improve rule parsing.
Do you need to update the core manually?
No. Clash Verge Rev's installer bundles the matching Mihomo core, so updating the client updates the core with it. There's also a "core management" screen to switch between stable / alpha cores, but regular users should keep the default stable.
If a node from a new provider won't connect, first confirm the client is on the latest version (which brings the latest core). An old core may not recognize a new protocol — the symptom is a node that never connects or fails the handshake.
This core upgrade shipped with v2.5.0; for its features see the v2.5.0 feature update, and for the follow-up fixes see the v2.5.1 update notes. To understand the protocol-vs-core picture, compare with Clash for Windows. If memory use feels high after a core upgrade, see why memory use runs high and how to handle it. Get the installer from the download center.