Practical position
Clash is the original rule-based proxy core in this ecosystem. It uses Clash YAML, accepts local HTTP, SOCKS, mixed-port or transparent proxy traffic, then routes requests to DIRECT, REJECT, a proxy node or a proxy group.
Positioning
Clash YAML, best for classic SS, SSR, VMess, Trojan, Snell, HTTP, SOCKS and basic proxy groups.
| Item | Meaning |
|---|---|
| Status | Historical mainline |
| Profile format | Clash YAML, best for classic SS, SSR, VMess, Trojan, Snell, HTTP, SOCKS and basic proxy groups. |
| Protocol check | Use the core/protocol matrix |
Best Use Cases
- Users who need old tutorials or existing historical profiles.
- Profiles using classic node protocols, Rule mode and basic DNS.
- Syntax reference for historical clients such as Clash for Windows or ClashX.
Compatibility Notes
Protocol support depends on the selected core, client build, operating-system permissions and profile syntax. Treat provider subscription names as hints, then verify the actual parsed node fields in the client log.
- Do not equate the Clash core with every Clash client; the client may use Mihomo now.
- Do not assume every new protocol is supported by the original core.
- An old profile can parse while newer fields are silently ignored.