Every environment includes a browser profile that stores persistent Chrome data — cookies, local storage, extensions, IndexedDB, cached credentials. When you attach an environment to a session, the browser starts with that saved state already loaded. Without a profile: every session opens a blank browser. You log in each time, re-accept cookie banners, and lose any site-specific data. With a profile: sessions pick up where you left off. Login cookies persist, preferences carry over, and previously saved data is available immediately.Documentation Index
Fetch the complete documentation index at: https://docs.webrun.ai/llms.txt
Use this file to discover all available pages before exploring further.
Use Cases
Skip Repeated Logins
Log in once, then reuse that session state across future tasks:- Create an environment and run a session with it attached
- Log in to the target site during the session
- The profile saves your login cookies automatically when the session ends
- Future sessions on the same environment start already authenticated
Preserve Site Preferences
Cookie consent choices, language settings, dark mode preferences, and other site-specific configuration carry over between sessions without any extra setup.Maintain Application State
For e-commerce or SaaS workflows, keep cart contents, workspace configurations, or application state intact between sessions.Profile Status
Each environment tracks the state of its browser profile:| Status | Meaning |
|---|---|
empty | No browser data yet — sessions start with a clean browser and populate the profile on exit |
uploading | A profile upload is in progress |
ready | Has browser data — sessions load the saved state before executing tasks |
Populating a Profile
There are three ways to get browser data into an environment’s profile:| Method | When to use |
|---|---|
| Run a session | Easiest — just run a session with the environment attached, log in, and the profile saves automatically |
| Sync from local Chrome | You’re already logged into sites locally and want to transfer that state |
Upload a .tar.gz archive | You have an exported Chrome profile archive to restore |
Using a Profile in a Session
PassenvironmentId when starting a session or task. The browser loads the profile’s saved data before executing anything:
Sync from Local Chrome
The sync command packages your local Chrome browser data and uploads it directly to an environment. This is the fastest way to populate a profile if you’re already logged into sites locally.Sync to an Existing Environment
If you’ve already created an environment, sync your local browser data to it:| Parameter | Description |
|---|---|
--environmentId | The ID of the environment to sync to |
--key | Your WebRun API key |
ready once the upload completes.
Create and Sync in One Step
To create a new environment and upload your local data in a single command, omit--environmentId:
Limits
| Resource | Limit |
|---|---|
| Environments per user | 20 |
| Profile upload size | 500 MB |
| Accepted format | .tar.gz, .tgz |
Environments Overview
What environments are and when to use them
Environments API
Create environments and upload profile data via the API