FlClash: Start Automatically When You Sign In

Opening the app is not the same as connecting the proxy

Searching for FlClash startup settings can lead to three different things: opening the app automatically, hiding its window, and automatically beginning proxy operation. This guide covers only opening FlClash when you sign in to Windows. It does not change subscriptions, nodes, DNS, or TUN, and it does not borrow menus from another Clash client.

The instructions cover the actively maintained FlClash v0.8.98 official release on Windows 11, for amd64 (x64) or arm64, using its English interface labels. The official app must already be installed or fully extracted and working when opened manually. These are not startup instructions for macOS, Linux, or Android. The installer and portable ZIP releases use the same setting logic. Keep a portable copy in a stable, accessible location; do not run it from an archive preview.

Setting	What it controls
Auto launch	Registers the current executable to start when the current Windows user signs in.
Silent launch	Hides the window when the app starts, leaving it in the background. It does not itself register a Windows startup entry.
Auto run	Helps determine whether the app enters its running state during initialization. It does not make Windows open the app automatically.

All three settings default to off in a fresh configuration for this version. Existing settings or a restored backup may differ. Enabling Auto launch does not also change Auto run, the system proxy, or TUN. Check separately whether your existing configuration resumes operation and whether the network connection works. A visible window is not proof that the proxy is connected.

Open Application from Tools and enable Auto launch

Use your regular Windows account and open FlClash from the location you intend to keep using. There is no need to create a scheduled task, add a Startup-folder shortcut, or edit the registry for these steps.

Open Tools and find the Settings group. Settings is a group heading here, not another page that you need to click.
Select Application. Note the current states of Auto launch, Silent launch, and Auto run before changing anything.
Enable Auto launch. For the first check, you can leave Silent launch off so the window is easier to spot. Keep Auto run and your other proxy settings unchanged.
Do not immediately quit or repeatedly toggle the switch. Allow the settings to synchronize, return to Tools, then reopen Application and confirm that Auto launch is still on.

This page has no separate overall Save button. The switch updates the configuration, which is saved automatically, while the Windows startup entry is synchronized asynchronously. There is no fixed number of seconds that guarantees success, and an enabled switch alone does not prove that Windows registration succeeded. Follow it with the sign-in check below.

Startup means after sign-in: This version registers startup for the current user; it is not a system service that runs before anyone signs in. Do not install a service, switch to running as administrator, or disable UAC just to enable this setting. If the device is managed by an organization and you see a policy or permission warning, check that restriction first.

Sign in again with the same account and check the app

Save your work in other programs, then sign out and sign back in to the same Windows account, or restart the computer and sign in. Locking and unlocking the screen is not the same test. Neither is closing the window and opening the app manually. Once the desktop appears, do not launch FlClash yourself: that would make it impossible to tell whether automatic startup worked.

Windows may delay processing startup apps, so a missing window immediately after sign-in does not establish a failure. Check both the desktop and notification area, including hidden tray icons if Silent launch is enabled. If necessary, use Task Manager to check whether the app is running, then open its panel from the tray. After the first successful check, restore or enable Silent launch if you prefer it.

The app opens, but a website does not: Automatic startup and network connectivity are different checks. Examine the existing configuration and running state; recreating a startup entry will not fix a node problem.
The app never starts: Confirm that you used the same account, the in-app switch stayed enabled, manual launch still works, and the executable has not moved. In Windows, open Settings → Apps → Startup. If a FlClash entry is present, check its enabled state; do not enable unrelated apps in bulk.
You moved the portable folder: Open the complete FlClash application from its new location. Turn Auto launch off and allow it to synchronize, then enable it again and repeat the sign-in test. Registration uses the actual executable path, not a generic download name that always points to the newest version.

These instructions are checked against the fixed-version implementation, not presented as a hands-on Windows test. A historical issue report does not establish a general defect in the current version. If security software, organization policies, or another user account is involved, record the exact message and app location first. Do not change permissions and switch proxy nodes at the same time.

Turn Auto launch off inside FlClash

Return to Tools, find Application in the Settings group, and disable Auto launch. Allow the change to synchronize and confirm that the switch remains off. If you temporarily changed Silent launch for testing, restore its previous state. You do not need to clear Auto run or the existing proxy configuration.

Make this change in FlClash rather than only disabling its entry in Windows Startup settings. This version synchronizes startup registration with its saved in-app preference each time it opens. If Auto launch is still enabled in the app, opening FlClash manually later may enable the Windows entry again. After turning it off in the app, repeat the same-account sign-in test to confirm that this setting no longer launches it.

Disabling startup does not quit the running app: It changes what happens at a later sign-in and does not delete subscriptions. If FlClash still appears automatically next time, first check for another copy or a startup method you previously configured yourself. Do not delete every similarly named task, clear the registry, or disable system security.

The outcome is straightforward: with the setting enabled, signing in to the same account opens the app; with it disabled, that startup entry no longer opens it. Only Auto launch and any temporary window-visibility change are needed. No patch download, core replacement, or command is required.

Official sources and version scope

Version numbers, filenames, and interface labels can change. Confirm them in the linked project documentation before making changes.