Two clients, two platforms — desktop and Android, built around Mihomo / Clash Meta.

The Nemux ecosystem — SlothClash & ClashFest
1 mins
177 words

Right now the Nemux ecosystem is mostly two clients built around mihomo / Clash Meta — same core philosophy, different platforms. Other repos will land here as they go public.

SlothClash — desktoph2

SlothClash is the desktop client for Windows, macOS, and Linux, based on clash-verge-rev.

Recent focus:

  • Fail-closed signed in-app updates (minisign + ed25519 verification)
  • Import local configs and proxy share links (vless://, vmess://, ss://, etc.)
  • UI polish — design tokens, warm light theme, cleaner Proxies and Rules flows

ClashFest — Androidh2

ClashFest is the Android client, based on Clash Meta for Android.

Recent focus:

  • Dedicated Profiles tab with collapsible proxy groups
  • Read-only config.yaml viewer per profile (debug what the app actually generated)
  • Simpler proxy chain setup — First hop → Exit, with explicit Save vs Use now actions
  • JNI hardening and security audit fixes

Why two clients?h2

Desktop and mobile have different constraints: TUN lifecycle, background services, UI patterns, update mechanisms, and how users import subscriptions.

SlothClash and ClashFest each go deep on their platform. Both pin the same Mihomo core and ship on a regular cadence. This devlog is where updates from across the Nemux ecosystem land in one place.