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 August 4, 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.
01
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 →02
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 →03
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 →04
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 →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.