Short answer

TrustTunnel is a newer Mihomo outbound type with TLS fields, health checks, QUIC and connection reuse options. In real use, trust the provider subscription first and then verify whether the selected client core supports this exact type.

What It Means

In Clash/Mihomo configuration, trusttunnel identifies the outbound type used by the node, policy or group. The same display name in a GUI can hide different transport fields, so the YAML or subscription output is more reliable than the node nickname.

Common Fields

type: trusttunnel
username / password
health-check
udp
sni / alpn
quic
max-connections / streams

When to Use It

The subscription explicitly contains trusttunnel.
The provider requires health-check or QUIC mode.
The client uses a recent Mihomo core.

Support Checks Checks

This is a newer type, so older clients may not recognize it.
quic and reuse parameters should follow the server profile.
TLS fields still affect handshake and certificate verification.

Minimal Shape

proxies:
- name: "trusttunnel-node"
  type: trusttunnel
  server: server.example.com
  port: 443
  username: user
  password: password
  health-check: true
  udp: true

Compatibility Notes

Client support changes with the bundled core. A maintained Mihomo-based client usually supports more modern node types than historical Clash clients, but mobile clients and iOS alternatives still vary by app and release.

If a subscription contains this type but the client filters it out, switch to a compatible client, ask the provider for a compatible subscription format, or use a converter only when you understand what fields are being changed.

Official Reference

TrustTunnel in Mihomo docs

TrustTunnel Protocol