Local utilitiesTOOL / 01

Write less.
Avoid mistakes.

Generate import links and process rules, then copy read-only diagnostics. Everything runs locally in your browser and is never uploaded.

01
URL SCHEME

One-click import link

Encode a subscription URL as a link ClashFX can open. Subscription URLs are sensitive—do not share the result.

02
RULE BUILDER

Route by process

Enter the actual macOS executable name to generate a mihomo PROCESS-NAME rule.

Run ls /Applications/App.app/Contents/MacOS/ and use the returned filename—not the display name or bundle ID.

TroubleshootingTOOL / 02

Isolate first.
Change second.

Check the base network, system proxy, node, configuration, and TUN in order. Change only one condition at a time.

01

Check the base network

Disable system proxy and Enhanced Mode. If the network still fails, ClashFX is probably not the cause.

02

Test system proxy only

Use a known-good node to verify the subscription and proxy path.

03

Then enable TUN

If failure starts here, check permissions, DNS, VPNs, and old network extensions.

Read-only diagnostic commands

Find the ClashFX processConfirm the app is runningps aux | grep ClashFX
Inspect listening portsFind conflicts on default portslsof -nP -iTCP -sTCP:LISTEN | grep -E 'ClashFX|7890|7891'
Inspect system DNSCompare DNS before and after TUNscutil --dns | grep nameserver
Open the configuration folderOfficial default directoryopen ~/.config/clashfx
Sanitize reportsRemove usernames, subscription URLs, node addresses, and IPs before filing an issue.