Just My Socks in Clash Verge Rev: Import the Native Mihomo Subscription
Sun Oct 25 2026
Just My Socks added a dedicated Mihomo / Clash.Meta YAML subscription on July 20, 2026. It lets compatible desktop clients fetch the configuration directly from your service. This guide covers the first import, checking that traffic uses it, and handling later updates. The feature and its compatibility requirements are documented in the JMS announcement.
Check the client and service first
You need an active JMS service and a current client using Mihomo, such as Clash Verge Rev. The original Clash and older ClashX cores cannot handle every protocol in the generated subscription. A familiar application name does not establish core compatibility: check the project’s documentation and installed version.
Use the Clash Verge Rev installation instructions to obtain the application for your operating system and processor. The JMS configuration includes the compatible Shadowsocks, VMess and VLESS Reality servers available with your particular plan; it does not add servers or entitlements beyond that plan.
Copy the correct subscription URL
- Sign in to the official JMS client area and open the service you want to use.
- Open Subscription and find the Mihomo / Clash.Meta YAML subscription.
- Copy its complete URL, keeping the private query parameters intact.
The client needs the subscription endpoint that returns a YAML configuration. A service details webpage, a single ss:// or vless:// server link, or a subscription intended for another client is a different input. Return to the service’s Subscription section if you are unsure which one you copied.
Treat this URL as a credential. Avoid pasting it into public issue reports, screenshots, online converters or shared documents.
Import and activate the remote profile
In Clash Verge Rev, open the subscription/profile area and use its remote subscription import option. Paste the YAML URL, complete the import, then select the resulting profile so that it becomes active. Depending on the version and interface language, the labels may differ; the official subscription guide describes the available import methods.
Check that the profile contains JMS servers and the expected groups before changing advanced settings. If the import returns a parse error, first verify the URL and client core. If it returns a connection error, examine whether the subscription endpoint itself is reachable; importing a profile and connecting to a server are separate operations.
For initial testing, keep a single client responsible for the system proxy. Several proxy or VPN applications changing the same settings can make the active route difficult to identify.
Choose JMS or JMS Auto
JMS provides manual server selection. Start with one server and test your usual website or application. This makes it easier to compare results and identify which route handled a request.
JMS Auto selects servers using latency measurements. A short delay to a test URL does not establish the fastest download throughput or guarantee access to a different service. Test the application you actually need. Automatic selection may also change the outgoing server; choose manually if you need a consistent route for a work session. Neither group implies a dedicated or permanently fixed IP address.
Turn on routing and verify it
Activate the client’s system proxy for applications that follow the operating system’s proxy settings. Importing a subscription alone does not route their traffic. The official quick start distinguishes system proxy from TUN mode, which captures traffic through a virtual network interface.
Use a browser to open a normal HTTPS page, then inspect the client’s connections or logs to check the matched rule and outgoing server. Repeat with the service you intend to use. A successful page load alone does not prove it used the proxy: rules may route some requests directly.
A terminal may not follow system proxy settings. For Claude Code or other command-line tools, see the terminal proxy guide. Use the local address and port displayed by your installed client rather than copying a port from another tutorial.
Refresh without losing local changes
Refresh the remote profile after JMS changes server details. Check that the refresh succeeded and the intended profile remains active. Direct edits to a downloaded subscription can be replaced by the next refresh. Keep a backup and use the client’s documented extension configuration or script features for persistent customizations; check their precedence before applying them.
If a particular Reality server still fails after a successful import, follow the VLESS Reality troubleshooting guide. For other devices, use the download and setup guides. Subscription refresh repairs outdated configuration; it does not resolve every remote server, DNS or account problem.
Compare JMS plans, traffic allowances and locations before choosing a service. This independent guide contains an affiliate link: we may receive a commission if you purchase through it.