How z-siqi/clash-for-windows_chinese works
This repository supports a modified Clash for Windows application, documented as offering a choice between legacy Clash and Mihomo cores, including AnyTLS support. The supplied tree and excerpts do not expose the main application implementation, so its documented capabilities are represented as subsystems without inferred call paths. The excerpts do show a Linux service helper that manages a proxy-core process and serves HTTP endpoints, plus TAP multicast packet policy. Release packaging code is omitted because it is build infrastructure, not product runtime.
Main entry points: main Core selection · main.go Linux service HTTP · packet_policy_cli.go Packet policy CLI · policy.go Service policy
Components 13
Application capabilities
- Clash for Windows
app/main - Core selection
app/main - Mihomo core
app/main - Legacy Clash core
app/main - AnyTLS editing
app/main
Linux service
- Service API client
app/main - Linux service HTTP
scripts/native/linux-service-helper/main.go - Core process manager
scripts/native/linux-service-helper/main.go - Service policy
scripts/native/linux-service-helper/policy.go
TAP forwarding
- Packet policy CLI
scripts/native/tap-forwarder/packet_policy_cli.go - Multicast policy
scripts/native/tap-forwarder/multicast_policy.go - TAP tunnel library
Other components
- Desktop user
Connections 8
- Desktop user → Clash for Windows: uses
README.md - Clash for Windows → Core selection: offers
README.md - Core selection → Mihomo core: selects
README.md - Core selection → Legacy Clash core: selects
README.md - Mihomo core → AnyTLS editing: supports
README.md - Linux service HTTP → Core process manager: starts and stops
scripts/native/linux-service-helper/main.go - Linux service HTTP → Service policy: loads
scripts/native/linux-service-helper/main.go - Packet policy CLI → TAP tunnel library: configures
scripts/native/tap-forwarder/packet_policy_cli.go