Open-source project
chen08209/FlClash avatar
chen08209/FlClash

FlClash runs the mihomo core on Android and three desktops, with a disclaimer gate and a Linux tray catch

A multi-platform proxy client based on ClashMeta,simple and easy to use, open-source and ad-free.

63,382 stars4,188 forksDartGPL-3.0

At a glance

What is it?
A guide to FlClash, the GPL-3.0 Flutter client for the mihomo (Clash.Meta) core: which package to download per platform, how profiles and Android automation work, and the setup details that stop it from running as expected.
Who is it for?
FlClash fits people who already have a Clash or mihomo subscription and want one open-source, ad-free client across Android, Windows, macOS and Linux, including Android TV and ARM laptops. It is not an option for iPhone users, since iOS is not among its platforms.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Dart, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • chen08209/FlClash63,382 ★ · +13,592
Star history
Repository2026-08-242026-11-15
chen08209/FlClash49.8k63.4k

13,592 Stars in the last 83 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

One mihomo core across Android, Windows, macOS and Linux, but no iOS

FlClash is a Flutter app, written in Dart, wrapped around the mihomo (Clash.Meta) core. That core supplies rule routing, proxy groups, latency tests, system proxy and TUN mode, and the app adds live views of connections, requests, DNS queries and logs. Platform-specific extras differ by device: Android gets a Quick Settings tile, per-app proxy and Android TV support, while the desktop builds get a tray menu and global hotkeys. Desktop builds come in x64 and ARM64. The supported platforms stop at four: Android, Windows, macOS and Linux. There is no iOS or iPadOS build in the release table, so anyone hoping to use the same client on an iPhone has to look elsewhere. Settings and profiles can be backed up and restored through WebDAV or a local file, which is how you move a setup between your own devices.

Android ships three APKs, and most phones need arm64-v8a

Android releases come as separate APKs for arm64-v8a, armeabi-v7a and x86_64 rather than a single universal package. Most phones use arm64-v8a; armeabi-v7a covers older 32-bit devices and x86_64 covers emulators and x86 hardware. Picking the wrong file is the most common first mistake, and the project website at chen08209.github.io/FlClash picks the right file for your device if you are unsure. FlClash is also published through its own F-Droid repository rather than the main F-Droid catalogue. That repository is identified by the fingerprint 789D6D32668712EF7672F9E58DEEB15FBD6DCEEC5AE7A4371EA72F2AAE8A12FD, and you should compare that value when adding the repo to an F-Droid client, since the fingerprint is what ties the packages to this project.

Windows needs version 10, macOS needs 12, and Homebrew has a cask

On Windows 10 and later you choose between an installer (.exe) and a portable .zip, each for x64 and ARM64; Snapdragon and other ARM laptops should take the ARM64 build. macOS 12 and later gets a DMG for Apple Silicon and for Intel, so older macOS releases are out of scope. On macOS the app is also available through the developer's own Homebrew tap:

bash
brew tap chen08209/tap
brew install --cask flclash

The tap is chen08209/tap, not the default Homebrew cask list, so the brew tap line has to run first. The cask route makes upgrades part of your normal brew workflow; the DMG route leaves updating to you.

The AppImage and .rpm lose the tray icon without AyatanaAppIndicator

Linux builds come as .deb, .rpm and AppImage, each for x64 and ARM64. Only the .deb package installs its own dependencies. With the AppImage or the .rpm, the tray icon will not show until the AyatanaAppIndicator library is installed on the system:

bash
sudo apt-get install libayatana-appindicator3-1
sudo dnf install libayatana-appindicator-gtk3

The first line is for Debian and Ubuntu, the second for Fedora. Because the tray menu is one of the desktop controls, a missing icon leaves you without that quick way to reach the app. On a Debian-based system the simplest fix is to use the .deb package in the first place.

The core does not start until someone accepts the disclaimer

FlClash starts the mihomo core only after its disclaimer has been accepted in the interface. On a normal desktop or phone you click through it once. In an unattended setup, such as a container or a machine nobody is sitting at, there is no one to click, and the core simply never starts. The fix is an environment variable set in the app's environment:

text
FLCLASH_ACCEPT_DISCLAIMER=1

With it set, the disclaimer is accepted on first launch. If you run FlClash headless and see no traffic routed, check this variable before anything in your profile.

Profiles import from a clash:// link, then accept overrides and custom rules

A profile comes from a subscription link or a local file. Once imported, it can be changed with a built-in editor, override scripts, and custom rules, proxies and proxy groups, so you can adjust a provider's subscription without editing the file they serve. Opening a link of this form imports a subscription directly:

text
clash://install-config?url=<URL-encoded subscription link>

The clashmeta:// and flclash:// schemes work the same way. The subscription address has to be URL-encoded inside the url parameter; pasting a raw link with its own query string into that position breaks the import.

Tasker and adb can start, stop or toggle the proxy on Android

On Android, FlClash exposes three activity actions that automation apps such as Tasker and MacroDroid can launch:

text
com.follow.clash.action.START
com.follow.clash.action.STOP
com.follow.clash.action.TOGGLE

The same actions work from a computer over adb:

bash
adb shell am start -a com.follow.clash.action.TOGGLE

This gives you rules like turning the proxy on when you join a particular network, without opening the app. The equivalent on the desktop is the tray menu and global hotkeys; no command-line control is offered there.

Building from source needs Flutter 3.47, Go 1.27 and Rust on each host

A source build needs Flutter 3.47 (release builds use 3.47.6), Go 1.27 and Rust installed through rustup. Each desktop platform builds on its own host; only Android builds anywhere.

bash
git clone --recursive https://github.com/chen08209/FlClash.git
cd FlClash
flutter pub get
dart setup.dart android

The Go core and Rust libraries compile during the Flutter build, and packages land in dist/. Android also needs the SDK and NDK, and --arch arm64 builds one ABI. Windows needs MinGW-w64 GCC and Inno Setup 6, macOS needs Xcode and Node.js for appdmg, and Linux expects Debian or Ubuntu. If you cloned without --recursive, make submodules fetches the Clash.Meta sources. Releases are still pre-1.0: v0.9.0, v0.9.1 and v0.9.2 shipped in October 2026, and the last push was 2026-11-01.

Editorial conclusion

FlClash fits people who already have a Clash or mihomo subscription and want one open-source, ad-free client across Android, Windows, macOS and Linux, including Android TV and ARM laptops. It is not an option for iPhone users, since iOS is not among its platforms. Before deploying it, check which Android ABI or desktop package you need, install the tray library if you use the AppImage or .rpm, and set FLCLASH_ACCEPT_DISCLAIMER=1 on any machine where nobody can click the disclaimer.

Frequently asked questions

What is FlClash used for?

FlClash is a proxy client built on the mihomo (Clash.Meta) core for Android, Windows, macOS and Linux, offering rule routing, proxy groups, latency tests, system proxy and TUN mode.

How do I add a profile to FlClash?

Import a subscription link or a file in FlClash, or open a link of the form clash://install-config?url= followed by the URL-encoded subscription link. The clashmeta:// and flclash:// schemes also work.

How to install FlClash?

Download the build for your platform from GitHub Releases or the project website, which picks the right file. On macOS you can also use brew tap chen08209/tap and brew install --cask flclash.

Is FlClash safe?

FlClash is open source under GPL-3.0 and ad-free, and it can be built from source with Flutter, Go and Rust. Its F-Droid repository is published with a fixed fingerprint you can check.

Official sources

  1. Official README
  2. Project repository
  3. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/chen08209-flclash.svg)](https://hysenlabs.com/projects/chen08209-flclash)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/chen08209-flclash.svg)](https://hysenlabs.com/projects/chen08209-flclash)

Was this useful?