Current means documented
A capability is described as current only when it belongs to the reviewed public product scope.
Product capabilities
Agilelogin brings persistent browser Profiles, visible network assignments, and local automation controls into one desktop workspace. These pages explain what each capability does, where its boundary ends, and what remains the operator's responsibility.
Product documentation · Last reviewed October 14, 2026
Agilelogin is a pre-release desktop browser workspace for authorized multi-account work and AI-agent automation. Its current public scope centers on named Profiles, browser-state separation, per-Profile proxy configuration, explicit local CDP and REST control surfaces, and the Chromium-based Polychrome kernel. No public installer is available yet.
Start with the capability that answers your question, then review its limitations before designing a workflow around it.
Give authorized work a named, persistent browser context with identifiable state.
A Profile separates browser state; it does not replace device access controls or grant account permission.
Read the details →Create or move many Profiles and proxies with a CSV or JSON file, and check a row-by-row preview before anything is saved.
Proxy passwords and cookies are exported only when you tick them, and then in plain text.
Read the details →Connect approved tools through explicit local CDP and REST surfaces.
A local interface does not make every script, dependency, or instruction safe or authorized.
Read the details →How the parts behind each Profile work, and where each one stops.
Keep the intended network route visible alongside the Profile that uses it.
The proxy service remains a separate provider with its own credentials, availability, and data practices.
Read the details →Run the Chromium-based kernel designated for Agilelogin's first desktop releases.
A public installer and release-specific compatibility details have not been published yet.
Read the details →Set a Profile's identity, hardware, region, canvas and audio settings, fonts, media devices, WebRTC and geolocation in one place, with consistency checks before you save.
The checks find settings that contradict each other; they do not predict how any website will judge the Profile.
Read the details →Import, export and copy a Profile's cookies in Netscape, JSON or EditThisCookie format. Each Profile's cookie store is encrypted with its own local key.
Cookies stay on this computer and are not synced; an exported file is plain text that you keep.
Read the details →Three WebRTC modes with Privacy as the default, and a kernel that keeps DNS, user agent and language on the Profile's own route.
A Profile cannot sign in to a browser account, and no mode makes a Profile unidentifiable.
Read the details →Free account
Profiles, proxies, groups, and the extension list are encrypted on your device before upload, and we keep a copy of the key so you can restore them when you sign in. Account preferences are stored unencrypted. How sync handles your data
Compare Free and Pro →A capability is described as current only when it belongs to the reviewed public product scope.
Future engines, interfaces, or collaboration features remain labeled as planned until a release proves otherwise.
Product controls help structure work but cannot promise third-party account, network, or website outcomes.