Browser session settings
Set how many browser sessions run at once, how long they live and how much memory, display and network they may use.
Where the settings are
Find them in Settings → Plugins → browser. Every field is optional and uses the default below when unset.
The form has six groups: Runtime, Timeouts, Streaming, Control, Resource limits and Network. Those group names are headings, not values.
Runtime and timeouts
| Setting | Key | Default | Range |
|---|---|---|---|
| Chrome executable | chromeExecutable |
Detect automatically | Optional path; advanced |
| Maximum active accounts | maxActiveUsers |
4 | 1–20 |
| Maximum tab sessions per account | maxSessionsPerUser |
2 | 1–8 |
| Idle timeout | idleTimeoutMinutes |
10 minutes | 1–60 minutes |
| Hard session limit | hardSessionLimitMinutes |
60 minutes | 5–240 minutes |
| Process close grace | browserCloseGraceSeconds |
15 seconds | 0–120 seconds; advanced |
Viewing
| Setting | Key | Default | Range |
|---|---|---|---|
| Display width | maxViewportWidth |
1280 px | 800–1920 px |
| Maximum viewers per display | maxViewersPerSession |
4 | 1–8 |
| Update coalescing | vncDeferMs |
10 ms | 5–400 ms; advanced |
| Takeover lease | takeoverLeaseSeconds |
120 seconds | 30–600 seconds |
Resources and network
| Setting | Key | Default | Range |
|---|---|---|---|
| Chrome memory per account | maxChromeRssMb |
768 MiB | 256–2048 MiB |
| Maximum Chrome targets per account | maxTargetsPerUser |
12 | 4–32 |
| Maximum concurrent proxy connections | proxyConcurrency |
96 connections | 1–200; advanced |
| Maximum proxy requests per minute | proxyRequestsPerMinute |
3000 | 30–6000; advanced |
| Private network allowlist | privateNetworkAllowlist |
Empty | Hostnames or CIDRs; advanced and high risk |
An empty allowlist blocks private, loopback, link-local and metadata addresses. Add an entry only for a local development target, as described in Browser network access.
What happens at a limit
Activity from the agent, from you or from a viewer keeps an idle session alive, but the hard lifetime limit still applies while you hold control.
A new session is refused when the account already has its maximum sessions or the instance has reached its active-account limit. When Chrome passes its memory ceiling, the oldest idle session closes, and a fresh launch keeps the account profile.
Chrome also limits pages, popups and workers per account. A new target over that limit is closed.
Status checks
The Status panel in the plugin detail shows live capacity, isolation, dependencies and limits. Its five checks cover Chrome, browser control, the virtual display, the network proxy and profile storage. A blocked dependency prevents sessions from starting, and each blocked check suggests a fix.
The panel reads data only. The browser sandbox and the DevTools connection are verified on the first managed launch, so a green panel alone cannot promise that a session will start.