Chute Devs

Hello everyone.

The biggest reason people stay on a proxy client they already know is inertia: switching usually means rebuilding your configuration from scratch in the new app’s own format. That was true of Chute, too — until now.

Starting with this release, Chute can import what you already have. Drop in a share link you copied from a friend, or a whole Clash / sing-box profile, and Chute converts it into native configuration. What you get back is an ordinary Chute profile — [Proxy], [Proxy Group], [Rule] sections — not a foreign file Chute keeps reinterpreting on the fly.

Two Kinds of Input

Share links. The single-node links you already know from every other client:

ss://, vmess://, vless://, trojan://, hysteria2:// (and hy2://), tuic://, anytls://, socks5:// (and socks://), and ssh://.

Each becomes a policy with the right type, port, TLS, SNI, transport and fingerprint options filled in for you. The text after the # becomes the policy name.

Whole profiles. Three formats, detected automatically:

A http:// or https:// address is treated as a subscription: Chute downloads the content first, then imports whatever the body turns out to be.

Conversion Is Forgiving on Purpose

Most real-world configs are messy. They use a provider you don’t support, a rule type with no equivalent, or a proxy type nobody should still be running. A converter that refuses the whole file over one bad line is useless.

Chute converts entry by entry. Every proxy, group and rule is converted on its own. The ones with no Chute equivalent are skipped and reported — with a warning written into the converted text right next to the section it came from, so you can see exactly what was dropped and why. A profile that is 95% convertible still imports and runs; only a file where nothing parses at all is rejected.

Two things worth saying out loud so there are no surprises:

• Proxy chaining is not implemented. mihomo’s dialer-proxy, sing-box’s detour, and Clash relay groups all describe a chain of proxies; Chute does not chain outbound traffic, so those policies connect directly to their own server instead.
• A converted profile is a static snapshot. If the source was a subscription that needed converting, the result is saved without an auto-update URL, so it will not refresh itself.

Using It

On iOS, import is available from every entry point — QR code, clipboard, a file, or a pasted URL — so getting your existing setup into Chute is now a scan or a paste away, not an afternoon of transcription.

1

trojan://[email protected]:443?sni=example.com&alpn=h2,http/1.1#Tokyo%20Node

becomes a policy named Tokyo Node, TLS on, SNI and ALPN set, ready to be routed like any other.

What This Means

For the first time, the cost of trying Chute is close to zero. If you have a config that works somewhere else, you can now see how it behaves inside Chute’s engine in minutes. And because the result is native configuration, everything Chute already does — the rule engine, policy groups, the dashboard, scripting — works on it immediately.

Full conversion details, including exactly which Clash and sing-box fields map where, are in the Chute Manual import page.

Thanks.

Chute Devs