2 versions of Sloth Clash are listed here, from November 10, 2026 to the current 0.10.1. Each one links to the publisher’s own installer files.
| Version | Date | Size | Files |
|---|---|---|---|
| 0.10.1Latest | November 14, 2026 | — | 64-bit EXE (NSIS)ARM64 EXE (NSIS) Release notes> ℹ️ You may be asked once to reinstall the helper service after this update: the core changed. On Windows the installer handles it; on macOS and Linux click the banner and accept the prompt.
🧩 XHTTP: share links with data in headers work
- XHTTP nodes that send upload data in request headers or cookies (uplink-data-placement: header or cookie) without an uplink-data-key now use the standard names X-Data-0, X-Data-1, ... (x_data_0, ... for cookies), as Xray servers expect. Before, such nodes sent headers named -0, -1 and never connected; share links leave the key out when it is the default, so they were affected. Nodes with an explicit key are unchanged.
🔒 XDrive: templated storage refused
- XDrive nodes with service: template are now refused, like service: local already was, wherever they come from: subscriptions, providers, manual and local profiles. A template lets the config choose the method, address, headers and body of HTTP requests sent from your computer, including to devices on your local network, as soon as a node is tested. Such a node keeps its name but shows as disabled and carries no traffic; Google Drive XDrive nodes are unaffected.
🔧 Fixes
- VLESS over XDrive: one slow or cancelled connection no longer breaks every other connection sharing the same XDrive session; a session whose storage stops accepting writes for 30 s is dropped and replaced; idle sessions close after 16 s instead of polling the storage forever. Storage HTTPS now trusts the same certificate roots as the rest of the core.
- An XDrive node on a storage service this app does not run (anything but Google Drive, for example s3 from newer Xray or a misspelled name) no longer makes a whole subscription or provider fail to load; the other nodes work. In profiles the app builds, that node shows as disabled (REJECT); in providers the core downloads itself, it fails when used with xdrive service "s3" is not supported by this build and sends nothing over the network.
- The subscription User-Agent now says which Citrus release the client is compatible with, the way Citrus itself does: clash.meta/v1.19.34 citrus/v1.0.0-beta.3 SlothClash/0.10.1. Panels that serve Citrus features by the citrus/ token now recognise SlothClash; the capability list in brackets is gone. The clash.meta/ prefix and the core version stay first, so format and protocol selection on other panels is unchanged.
- gRPC proxies: a server that sends a long run of empty gRPC frames can no longer crash the core (the reader used to call itself once per frame); a frame whose payload length is larger than its message is now refused.
- XHTTP: read and write deadlines are now separate and only end an operation that is still running when they pass. Before, any deadline closed the whole connection even while it was idle, and setting one direction moved the other, which could drop idle multiplexed (smux, yamux) sessions over XHTTP.
- A broken vless:// or vmess:// link in a subscription the core downloads itself no longer writes the whole link, with its UUID and keys, to the log; the warning names only the server and the node.
- A config or subscription with external-ui: ./ (or any directory that holds the core's own files) no longer makes the core serve its working directory, the running config with its secret and node credentials included, at /ui without the controller password. The dashboard is turned off for such a config with a warning in the log; dashboards in a subdirectory such as ui work as before.
- Closing an inbound listener (SOCKS, HTTP, mixed, Shadowsocks, VMess, VLESS, Trojan and others) while its accept loop was still running was a data race in the core. No crash or wrong behaviour from it has been seen; it showed up only in the core's own race-detector tests, where a listener is closed twice. The flag the two sides share is now synchronized.
- A node with a malformed per-proxy reality-opts.client-version no longer makes the whole subscription fail to load: the value is ignored wit |
| 0.10.0 | November 10, 2026 | — | 64-bit EXE (NSIS)ARM64 EXE (NSIS) |