Deep dives into Clash configuration: importing subscriptions, splitting traffic by rules, running TUN mode, and the practical details that separate a working setup from a smooth one. Subscription import failures, rule-set updates and node switching in Clash Verge Rev show up here more than anywhere else.
Hot Topics · 33 articles
33 articles covering Clash hot topics, from fundamentals to hands-on steps. Read them in order or jump straight to the part you need.
If you live on both Mac and iPhone, this guide compares Stash and Clash Verge Rev where they actually compete (macOS), clarifies what iPhone can and cannot run, and turns subscription import, TUN-style capture, routing depth, residency, and power into a practical checklist you can apply today.
Claude Code lives in your shell, not in a browser tab. When model calls, login, or self-updates stall while websites load fine, the culprit is usually routing: GEOIP direct rules, DNS that bypasses Clash, or a CLI stack that ignores system proxy. This guide maps Anthropic API traffic and typical dependency lanes into explicit Clash rules, then shows how to verify each hop without blindly flipping to global tunnel mode.
Selecting a Clash-compatible subscription should be deliberate: decode route buzzwords such as IEPL and IPLC, design honest speed runs, scrutinize quotas and concurrency, and insist on workable support—and terms you can rely on—before you pay for a year upfront.
Q2 stocking and ads: Temu and Shein seller backstage—onboarding, tickets, Ads console—timeouts while Slack works behind Clash: log-first DOMAIN-SUFFIX above GEOIP, MARKETPLACE_SELLER vs CDN groups, DNS fake-ip and TUN, gsp-style edges mis-routed DIRECT or wrong node before 618—cross-border sellers, not Prime Video or Netflix hostname dumps.
Prime Video region banners or stuck playback behind Clash while generic proxy works: log-first DOMAIN-SUFFIX for primevideo.com and recurring aiv-* style Amazon Video edges before GEOIP, dedicated PRIME_MEDIA proxy-groups versus retail amazon.com splits, DNS fake-ip aligned with Mihomo—not Netflix nflx-, Disney+ BamGrid-, Max Warner-, or YouTube googlevideo-only lists.
Epic Games Launcher weekly free claims or 0 B/s downloads while browsers work through Clash: DOMAIN-SUFFIX epicgames.com-shaped hosts ahead of GEOIP, Epic Web vs CDN proxy-groups, DNS fake-ip and TUN—not Steam steampowered lists; EOS login helpers, sale peaks, Sniffer for IP-only shards, subscription provider order, checklist—distinct Valve Steam UDP guide.
YouTube wrong region or Premium mismatch behind Clash: DOMAIN-SUFFIX youtube.com and googlevideo.com in a YOUTUBE_STREAM-style group before GEOIP, DNS fake-ip/TUN without leaks, Sniffer for IP-only googlevideo TLS, nodes aligned with Google account—not Netflix Open Connect lists.
Figma canvases stall, Live embed blanks, realtime cursors vanish behind Clash: DOMAIN-SUFFIX figma.com and static/embed CDN paths through a FIGMA strategy-group ordered before GEOIP, DNS aligned with fake-ip and TUN, Sniffer sparingly—design SaaS checklist, not Steam, Nintendo, Netflix, HF LFS, or AI-only host dumps.
ChatGPT works but OpenAI Sora or the video page spins: Clash DOMAIN-SUFFIX for sora.openai.com, openai.com, oaistatic.com, and chatgpt.com with rule order before GEOIP—video and CDN traffic distinct from api.openai.com chat rules; DNS fake-ip, TUN, Sniffer for IP-only edges; log-first checks—complements the ChatGPT and Claude article, not a duplicate host list.
Hugging Face Hub downloads stall while pages load: Clash DOMAIN-SUFFIX for hf.co and huggingface.co, Git LFS and cdn-lfs-style hosts, dedicated HF_HUB proxy-groups before GEOIP, DNS fake-ip and TUN alignment, Sniffer for IP-only CDN flows, stable nodes for large checkpoints—developer artifact delivery, not OpenRouter or Cursor API hostname recycling.
Windsurf opens but Cascade or Codeium spins: Clash DOMAIN-SUFFIX for official codeium.com, windsurf.com, codeiumdata.com families, dedicated proxy-groups before GEOIP, DNS and fake-ip alignment, log-first verification, Windsurf proxy UI per docs—toolchain split distinct from the Cursor IDE marketplace and *.cursor.sh guide.
Max (HBO) not available in your region behind Clash: log-first DOMAIN-SUFFIX for Warner streaming hosts, dedicated MAX_STREAM-style proxy-groups before GEOIP, DNS fake-ip and TUN without leaks, Sniffer for IP-only TLS, nodes that match your plan—complements Netflix and Disney+ articles, not the same domain paste.
Firefly and Creative Cloud behind Clash in 2026: sign-in spinners and empty panels from split identity versus library paths; log-derived DOMAIN-SUFFIX for adobe.com, adobe.io, adobelogin.com, typekit.net; dedicated ADOBE_CC proxy-groups before GEOIP; DNS fake-ip with TUN for desktop agents; Sniffer for IP-only TLS; verification before node swaps—not ChatGPT or Cursor hostname recycling.
Switch 2 eShop stalls or online drops while PCs work through Clash: log-first DOMAIN-SUFFIX for Nintendo CDNs and account hosts before GEOIP, separate NINTENDO_CDN proxy-groups, DNS fake-ip or TUN alignment, Sniffer for IP-only TLS, UDP-honest nodes, and a firmware-ready verification pass—not Netflix domain paste.
Netflix opens but wrong catalog, low bitrate, or spinner: align DNS with fake-ip or hijack vs system proxy or TUN, put Netflix CDN DOMAIN-SUFFIX rules in STREAMING before GEOIP, use Sniffer when IP-only flows bypass domain rules, and pick stable egress for web, mobile, and TV—not Disney+ domain lists.
Model Context Protocol with Clash: MCP_TOOLCHAIN proxy-groups from log-derived DOMAIN-SUFFIX rows, first-match ordering before GEOIP, DNS fake-ip and TUN for CLI versus IDE capture, Sniffer for IP-only HTTPS, verification with logs and curl—complements Cursor IDE split rules, not a duplicate.
Disney+ “not available in your region” behind Clash: BamGrid and Disney+ domain patterns from logs, dedicated STREAMING proxy-groups ahead of GEOIP, DNS fake-ip and TUN alignment, node picks that match your account region—not generic AI domain lists—with verification and compliance notes.
DeepSeek behind Clash: DOMAIN-SUFFIX deepseek.com for API and chat, Volcano Engine CDN suffix rows from logs, a dedicated DEEPSEEK proxy-group ahead of GEOIP, DNS alignment with TUN or system proxy, and log-first verification—distinct from OpenRouter, Perplexity, and Western-only AI domain lists.
OpenRouter behind Clash: DOMAIN-SUFFIX openrouter.ai, a dedicated OPENROUTER proxy-group, first-match ordering before GEOIP, DNS fake-ip alignment with TUN or system proxy, and verification from connection logs to curl—distinct from Cursor IDE host lists and generic AI buckets.
When Perplexity loads but searches or API calls stall, fix split routing: DOMAIN-SUFFIX rules for perplexity.ai and related hosts, a dedicated proxy-group for long HTTP/2 streams, CDN-aware ordering ahead of GEOIP, DNS fake-ip alignment, and practical node picks—without treating AI traffic as one anonymous bucket.
Toolchain-focused Clash routing for Cursor IDE: separate proxy-groups for *.cursor.sh model APIs versus marketplace.cursorapi.com and CDN binaries, optional VS Code marketplace mirrors, DNS fake-ip alignment, HTTP/2 streaming pitfalls, and verification when the browser works but extensions or inline AI stall—distinct from ChatGPT-only split guides.
Split Google Gemini, AI Studio, and the Generative Language API in Clash: DOMAIN-SUFFIX inventory for generativelanguage.googleapis.com and Google OAuth hosts, a dedicated GEMINI proxy-group, DNS fake-ip alignment, rule order before GEOIP, regional node notes, and a short verification checklist distinct from ChatGPT-only rules.
Split Grok, xAI APIs, and X (Twitter) login in Clash with DOMAIN-SUFFIX rules, dedicated proxy-groups, DNS fake-ip alignment, first-match ordering before GEOIP, and a repeatable test plan when pages or API calls time out—without reusing ChatGPT-only host lists.
Windows still dominates the Clash user base, yet three names keep showing up in search results: Clash for Windows, Clash Verge Rev, and Mihomo Party. This guide compares maintenance status, Mihomo kernel support, TUN capture, UI depth, and subscription workflows so you can pick a client that still makes sense in 2026.
Google Gemini CLI is a free terminal AI agent that exploded in 2026, but OAuth login, API key checks, and model calls often time out while websites load fine. The gap is routing: shells ignore system proxy, GEOIP shortcuts steal first-match wins, and npm install traffic uses different hosts than generativelanguage.googleapis.com. This guide maps Gemini CLI into explicit Clash lanes and shows how to verify each hop without blindly enabling global tunnel mode.
OpenAI GPT-Realtime-2 and the Realtime API keep a long-lived WebSocket open on api.openai.com while streaming audio in both directions. Handshake failures, mid-session drops, and jittery latency often trace to Mihomo rule order, DNS that bypasses fake-ip, or SDK runtimes that ignore system proxy hints. This guide maps Realtime endpoints, compares TUN versus mixed-port capture, walks an OPENAI_REALTIME lane, and ties verification to live connection logs.
Agent Toolkit fans out across MCP endpoints on api.aws, IAM-controlled regional APIs, STS credential hops, IDE toolkit manifests on idetoolkits.*, and optional Amazon Q language-server paths—not one tidy hostname list. When AI coding agents stall inside Cursor or VS Code, the durable fix is Mihomo-first rule order, resolver alignment, and log-backed DOMAIN rows that leave domestic defaults untouched.
Claude workloads on AWS in 2026 still split across console sign-in, STS credential hops, regional Bedrock inference hostnames under amazonaws.com, and sometimes direct Anthropic API calls. Separate Mihomo lanes with explicit DOMAIN rows above blunt GEOIP, align DNS fake-ip with SDK capture, validate each hop via connection logs, then retry the smallest failing console or Invoke action instead of swapping nodes blindly.
When ChatGPT quietly defaults conversations through GPT-5.5 Instant but only web, plugins, or the OpenAI API feel laggy or time out, the culprit is often routing: carve ChatGPT plus OpenAI hostnames into Mihomo-era proxy-groups ordered ahead of GEOIP, align DNS fake-ip capture, tighten node selection for long SSE streams versus REST calls, and verify first-match hits from Mihomo logs rather than blaming the rollout headline.
Pick a household Clash setup: LAN-sharing PC vs OpenClash bypass vs Docker on NAS—with DNS coupling, QUIC notes, failover, and a 2026 migration checklist.
When Gemini Enterprise consoles feel fine yet Agent Builder or Vertex-backed Gemini APIs swing between 200-series success and stalled SDK calls, routing—not model quality—is often the bottleneck. Here is how to carve a repeatable Google Cloud policy lane in Mihomo-era Clash: OAuth alignment, narrowed googleapis inventories, disciplined rule order and DNS coupling that survives enterprise SSO—not a rebranded ChatGPT cookbook.
Codex desktop builds and Codex MCP plugins do not speak to a single pretty hostname. Model calls, platform metadata, CDN assets, attachment buckets, and auth hops spread across official OpenAI edges—then third-party MCP bridges add their own. When tool invocations stall while browsing looks fine, the usual culprits are first-match rule order, DNS that bypasses Mihomo, and IDE outbound stacks that ignore polite system proxy hints. This tutorial names the OpenAI-shaped surfaces, walks a concrete OPENAI_API lane in Clash Verge, and ties verification to live connection logs.
AWS MCP Server inside Cursor or VS Code fans out to STS, IAM, partition-specific APIs, console sign-in, and sometimes corporate IdPs—not a single chat domain. When connections flap or hang, the fix is usually Clash rule order, DNS that actually passes through Mihomo, and capture depth that matches the IDE host. This hands-on guide walks the AWS-shaped split path without hiding behind generic MCP labels.
Free and open-source. Supports Windows, macOS, Android, iOS, and Linux. Ready to use in 5 minutes.