This project provides a curated set of traffic splitting rules for the Clash proxy client, designed to optimize access to AI services, Web3 applications, educational apps, and developer download resources. It aims to improve user experience by intelligently routing traffic for specific applications and protocols, particularly addressing challenges with newer protocols like HTTP/3 (QUIC).

How It Works

The rule set is a modification of the ACL4SSR project, offering personalized routing configurations. Key rules include dedicated splits for US-based AI services (OpenAI, Claude, Gemini), ByteDance overseas AI, developer downloads (Docker, models), and Web3 applications. A notable feature is its approach to handling HTTP/3 (QUIC) traffic, which often uses UDP. By implementing a local REJECT rule for UDP traffic on port 443, it forces applications to fall back to TCP, which Clash can then efficiently encapsulate and route, even over protocols like Hysteria2.

Quick Start & Requirements

Users can integrate these rules into their Clash client by appending &config=https%3A%2F%2Fraw.githubusercontent.com%2Fszkane%2FClashRuleSet%2Frefs%2Fheads%2Fmain%2FClash%2Fkclash.ini to their existing subscription URL. No specific software prerequisites are detailed beyond the need for a compatible Clash client.

Highlighted Details

• Specialized rules for AI services including OpenAI, Claude, Grok, Perplexity, Google Gemini, and ByteDance overseas AI.
• Dedicated routing for Web3 applications and developer resources like Docker images and model file downloads.
• A mechanism to mitigate HTTP/3 (QUIC) issues by forcing TCP encapsulation via UDP rejection.
• Built upon and modifies the ACL4SSR project's rule structure.

Maintenance & Community

No specific details regarding maintenance, community channels (like Discord/Slack), or notable contributors are provided in the README.

Licensing & Compatibility

The README does not specify a software license, and therefore, compatibility for commercial use or closed-source linking is undetermined.

Limitations & Caveats

The UDP rejection rule, while beneficial for HTTP/3, may negatively impact certain game services that rely on UDP. Additionally, some AI services prioritizing HTTP/3 might still encounter connectivity issues if not fully managed by the rule set or client configuration.