Short answer

Mieru is a newer proxy node type in Mihomo, with TCP/UDP transport, port range, multiplexing and traffic-pattern 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, mieru 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: mieru
server / port or port-range
transport
username / password
multiplexing
traffic-pattern

When to Use It

The provider explicitly supplies Mieru configuration.
You need a port range or a specific multiplexing mode.
The subscription is consumed by a Mihomo-compatible client.

Support Checks Checks

Do not mix port and port-range casually.
transport must match TCP or UDP.
traffic-pattern is an advanced field; avoid line breaks or truncation when copying.

Minimal Shape

proxies:
- name: "mieru-node"
  type: mieru
  server: server.example.com
  port: 2999
  transport: TCP
  username: user
  password: password

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

Mieru in Mihomo docs

Mieru Protocol