Environments

An environment is a named container that bundles a browser profile (cookies, local storage, extensions, cached credentials), persistent file storage, and optional triggers for scheduled automation. Pass environmentId when starting a session and it loads that browser state and makes those files available: no re-authentication, no re-uploading.

Why Environments Matter

Without an environment	With an environment
Every session starts from a blank browser	Sessions inherit saved login state and site preferences
You log in every time	Log in once, reuse across all future sessions
Files must be uploaded on every run	Files persist and are available to any session
No shared state between tasks	Browser data and files carry over until you delete them
Recurring tasks require your own scheduler	Triggers run automatically on a schedule you define

What’s Inside

Browser Profile

Stores Chrome data (cookies, local storage, IndexedDB, extensions, cached credentials) and carries it from one session to the next. Log in once and every subsequent session on the same environment skips authentication. See Browser Profiles for details on how profiles work, including how to sync from your local Chrome.

File Storage

Files attached to an environment stay until you explicitly delete them. Any session running under that environment can access those files without re-uploading. Useful for reference documents, configuration files, templates, or any asset your automation uses repeatedly. See File Uploads for persistent and temporary upload modes.

Triggers

Schedule browser automation tasks that run automatically on a recurring basis under this environment. Each trigger inherits the environment’s browser profile and files, so scheduled tasks can access logged-in sessions and stored data without extra setup. Results are delivered via webhook, bot notification, or both. See Triggers for schedule types, delivery modes, and the full API reference.

Lifecycle

Create → Upload profile data (optional) → Upload files (optional) → Use in sessions → Delete

Create an environment with a name and optional description.
Upload browser profile data (.tar.gz) if you have existing state to restore, or sync from your local Chrome.
Upload any files sessions need to access.
Use the environment by passing environmentId when starting a session or task. The session loads the profile and has access to all stored files.
Delete when no longer needed. This removes the profile and all attached files.

Quick Example

Create an environment, then run a task with it:

# Create the environment
curl -X POST https://api.webrun.ai/environments \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "my-environment"}'

# Use it in a task
curl -X POST https://api.webrun.ai/start/run-task \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Go to my dashboard and export the monthly report",
    "environmentId": "<ENV_ID>"
  }'

Limits

Resource	Limit
Environments per user	20
Browser profile upload size	500 MB
Accepted profile format	`.tar.gz`, `.tgz`

Next Steps

Environments API

Create, list, and delete environments; upload profiles and manage files

Triggers

Schedule recurring browser automation tasks under an environment

Browser Profiles

How browser profiles work, sync from local Chrome

File Uploads

Persistent and temporary file upload modes

Getting Started

Concepts

Usage Guides

Integrations

API Reference

Capabilities

Troubleshooting

Environments

Why Environments Matter

What’s Inside

Browser Profile

File Storage

Triggers

Lifecycle

Quick Example

Limits

Next Steps

Environments API

Triggers

Browser Profiles

File Uploads

​Why Environments Matter

​What’s Inside

​Browser Profile

​File Storage

​Triggers

​Lifecycle

​Quick Example

​Limits

​Next Steps

Environments API

Triggers

Browser Profiles

File Uploads

Why Environments Matter

What’s Inside

Browser Profile

File Storage

Triggers

Lifecycle

Quick Example

Limits

Next Steps