Chromium foundation
Polychrome follows the Chromium browser-engine family, providing the web compatibility expected from a Chromium-based desktop environment.
Feature · Browser kernel
Polychrome powers the first Agilelogin browser environments
Polychrome is the Chromium-based kernel designated for Agilelogin's first desktop releases, running inside the Profile and control model managed by the workspace.
Product documentation · Last reviewed August 4, 2026Reviewed against the current public product scope by the Agilelogin product team.
What is Polychrome?
Polychrome is Agilelogin's Chromium-based browser kernel. It provides the browser process used by a Profile while the desktop workspace manages Profile identity, state, network configuration, and approved automation connections. Polychrome is identified as the shipping kernel in the current product direction, but no public Agilelogin installer or release-specific compatibility matrix is available yet.
Where the kernel fits
The browser kernel renders and runs websites; the surrounding workspace defines which Profile, route, and control context launched it.
Launched by a Profile
The kernel is not the workspace record by itself. It runs in the context of the selected Profile and its associated browser state.
Network follows configuration
The Profile's reviewed network assignment determines the intended route used when the kernel connects to websites.
Automation follows release support
CDP and other control behavior must be verified against the installed release and its published documentation.
Kernel responsibilities and external dependencies
Website compatibility depends on more than the engine name alone.
| Subject | Agilelogin boundary | Operator action |
|---|---|---|
| Browser rendering and web platform behavior | Provided by the Polychrome Chromium-based kernel | Confirm the released version against the websites and extensions required by the workflow. |
| Profile identity, state, proxy, and lifecycle | Managed by the Agilelogin desktop workspace around the kernel | Select and review the intended Profile before launch. |
| Destination websites and third-party extensions | External software and services | Review compatibility, permissions, data practices, terms, and updates independently. |
How to evaluate a kernel release
Use release-specific evidence instead of assuming that every Chromium behavior or extension will be identical.
- STEP 01
Start from the official download page
Use only the installer, version, publisher, and integrity information published on agilelogin.com.
- STEP 02
Check the release notes
Confirm the Polychrome version, supported operating systems, known limitations, and automation compatibility for that build.
- STEP 03
Test the required workflow
Validate necessary websites, extensions, proxy behavior, and approved automation in a non-critical environment first.
- STEP 04
Plan updates and rollback
Record the known-good version and state-handling procedure before changing a browser kernel used for important work.
Current release boundaries
The kernel page documents direction without presenting an unreleased installer as available.
- No public desktop installer, exact Polychrome version, or supported extension list is currently published.
- Chromium-based does not mean every Chrome feature, service, policy, or extension is guaranteed to work.
- Polyfox is planned and must not be treated as a currently shipping alternative until its status changes publicly.
Questions about Polychrome
Is Polychrome the same as Google Chrome?
No. Polychrome is described as Chromium-based. Chromium is an open-source browser-engine foundation, while Google Chrome is a separate product with its own services, packaging, and policies.
Can I download Polychrome now?
No official public Agilelogin installer is currently available. Use the Download page as the source of truth and do not rely on third-party files claiming to be a release.
Does Polychrome support every Chrome extension?
No blanket compatibility claim is made. Extension support can depend on the released kernel version, extension permissions, browser policies, and the extension itself. Test required extensions against the official build.
Use release-specific facts
Check the official desktop release page for verified installers and compatibility details when they become available.