A GUI proxy client for Windows / macOS / Ubuntu Desktop based on Clash and Electron

• Easy to use interface.
• Build-in Clash binary.
• GUI configuration.
• Remote subscription support.
• Server speed test.
• Set as system proxy (Windows & macOS only).
• Start with system.

Download latest release from Release Page

Check "Sign Issue" for more information.

• Clone this project & run yarn install
• Run node pre-build.js to download clash binary for current platform.
• Run yarn start to start dev server for webpage.
• Run yarn start:electron to start electron main process. Or hit run button in VSCode.

• Run yarn run pack and wait.

• Where is my configuration files & how can I modify them?

  To check your configuration files for Clash & Clashy, click on the folder icon in status panel. Clash configuration file folder will opened automatically and navigate to parent folder you will see Clashy configuration files named clashy-configs.

• Can I change clash external controller port & secrets in configuration file?

  You can but you need to modify Clashy's source code to make it work.

• Auto update
• Post build script to zip binaries
• Reset system proxy after exit app
• Logout current clash client
• Use external clash binary
• Login interface for external clash binary
• Clash binary update
• View Clash logs
• Subscription auto-update

Any pull request is welcome.

Not exactly. I've been using ClashX for several months and I like it. It's easy to use and nicely designed. But I also need a decent Clash client on my Ubuntu Desktop. And the interface must be easy enough for anyone to use because I don't want to teach my wife how to edit proxy rules or how to use remote configuration files. So I decide to make my own Clash GUI client. I did NOT take any code or assets from those two projects but they did give me some ideas about interface design and implementation.

You can't for now. Visit 127.0.0.1:2390/logs for Clash logs.

Not really. Clashy use Clash's /delay API for speed testing. This API requires a parameter which indicates speed test timeout. This parameter is 10 seconds in current build. So there are two kinds of timeout in Clashy:

• Proxy timeout, which means proxy is unavailable.
• Clash speed test timeout, which means Clash waited more than 10 seconds but still no response from target server (which is https://www.google.com). This proxy might be available with a huge delay. Or unavailable at all.

Sadly, I can't distinct those two timeout types with current Clash API.

Me either. Checkout Electron memes below!