Sessions, billing, and authenticated browsers
How browser leases, idle timeouts, usage allowances, and local authentication-state imports work.
Browser lifetime and idle timeouts
Each launch creates an isolated cloud browser with a fixed maximum duration. A browser that is live but unused still occupies a concurrent-browser slot and can consume billable browser time. Tabfleet closes idle browsers after the configured inactivity timeout; the default dashboard timeout is 10 minutes. End a browser when the task is complete. Unused reserved Tabfleet allowance returns when the session closes.
Cloudflare Browser Run charges Browser Sessions for browser duration and concurrency. The provider may close a session after its keep-alive timeout, even when the browser tab is still visible.
Import an authenticated browser session
A normal webpage cannot read HttpOnly cookies, so copying document.cookie is not sufficient for many OAuth logins. Use the Tabfleet Session Exporter extension, or agent-browser locally, to create a native browser state file. The state file contains sensitive authentication material and should never be committed to source control.
Using the Tabfleet Session Exporter
Install the unpacked Tabfleet Session Exporter extension, open the authenticated page in Chrome, and choose Export session state. Enter additional cookie domains such as accounts.google.com when the identity provider is separate from the application. In the Tabfleet launch dialog, upload the downloaded JSON file and use the protected page as the start URL. The export is used for that launch and is not saved by Tabfleet.
When authentication expires
Authentication can still expire or be revoked by the application or identity provider. If the cloud browser redirects to /login, export a fresh state from the local extension and launch a new browser. A persistent browser lease cannot override Google or application session policy; unattended workflows should use a supported API token or service account when available.