If a Profile will not start after installation, allow the browser kernel process in your antivirus and firewall; it is a second program the app downloads on first launch.
Applies to: Agilelogin for Windows, first release.
The two programs
Agilelogin is two programs. The app you installed manages Profiles, proxies and settings. The browser kernel, Polychrome, is what actually opens a Profile’s window. On Windows it runs as polychrome.exe, spelled in lowercase, and lives under the app’s local application data folder in a kernels\<build>\ directory, one directory per installed kernel build.
The kernel is downloaded by the app on first launch, so an antivirus product sees a new executable appear and start without an installer. Some products quarantine it on that basis.
What should you allow?
- Antivirus: add
polychrome.exeto the allowlist, or the wholekernelsfolder under Agilelogin’s local data. - Firewall: allow outbound connections for
polychrome.exe. A Profile’s web traffic goes through the proxy configured for that Profile, so the kernel needs to reach the proxy’s address. - The app itself needs outbound access to
api.agilelogin.com(account and sync) andreleases.agilelogin.com(kernel downloads and app updates).
Both names are lowercase. The app checks the kernel directory’s shape exactly as published, so a renamed or recased executable is not recognised.
What if the kernel was quarantined?
The app reports that no usable kernel is installed and the Profile does not start. Then:
- Restore
polychrome.exefrom quarantine, or add the exclusion first and let the app download the kernel again. - Open Settings → Kernels and choose Check for kernel updates, or launch the Profile again: the app re-downloads the build it needs.
A scan that holds a file open can also delay the app’s own cleanup of old kernel builds. The app retries on its next start; nothing needs to be deleted by hand.