Lexmount BrowserCapability FAQ
Understand persistent contexts, custom extensions, proxies, and stored downloads in Browser plans.
This FAQ explains the capability names used in the Pricing comparison. Availability follows the selected project's current plan and the console. See the linked SDK capability pages for exact request parameters.
What is context persistence?
A Context is reusable browser state that can outlive a Session. Mounting a Context read-write lets website sign-in state, cookies, and browser storage be written back and reused by later Sessions. It is useful for authenticated or multi-step workflows.
It does not keep one Session running forever, and it does not preserve screenshots, replays, or downloaded files. An active read-write Session locks its Context. Close the Session normally before another task reuses that Context.
What are custom extensions?
Custom extensions let you upload a .zip or .crx browser extension and mount it by extension ID when creating a Chromium Session. They are useful for approved page enhancements, internal integrations, and automation helpers.
Extension code runs inside the remote browser, so upload only code you trust and are authorized to use. An extension cannot be deleted while an active Session uses it. Non-Chromium browser types such as Moli do not support Chromium extensions.
What is a custom proxy?
A custom proxy is an upstream proxy endpoint and credentials supplied by you. Once configured during Session creation, that Session sends website traffic through the selected proxy. Typical uses include your own network, a fixed egress path, or an authorized regional proxy.
Availability, performance, location, and compliance depend on the proxy provider. Never commit proxy credentials or write them to public logs. A custom proxy and the Lexmount official proxy pool are separate modes and cannot be enabled on the same Session.
What are file downloads?
File downloads let the remote browser save downloads triggered by a website into Session download storage. Through the SDK, a task can list files, retrieve one file, download an archive, or clear the Session's downloads.
The download happens in the cloud browser; it is not automatically written to the Agent's local working directory. Retrieve anything that must be retained before Session cleanup, then store or delete it according to your data-handling requirements.
What is the official proxy IP pool?
The official proxy IP pool is proxy egress integrated and managed by Lexmount. A Session can use the platform proxy without you supplying a separate upstream proxy account. Current regions, availability, and traffic allowances are shown in the console.
It does not guarantee a dedicated or permanently fixed IP for every Session, and it must not be used to evade a target site's rules. You remain responsible for applicable law, site terms, and project authorization. Official and custom proxy modes cannot be enabled together on one Session.