Lot

Cookie Setup for Verify

If your app requires authentication to test, you can provide cookies and localStorage entries so the automated browser verifier can access protected pages.

Prerequisites

  • Browser verification enabled — your project must have the browser verification capability enabled (set during project creation or in project settings)
  • Large sandbox recommended — browser verification runs a real browser alongside your dev server, so the large sandbox size (4 vCPU, 8 GB) is highly recommended

The Verify tab

Open any session and switch to the Verify tab in the right-side panel. You'll find two things here:

  • Auto-verify toggle — a checkbox at the top that controls whether the agent automatically runs browser verification after code changes
  • Browser state editor — where you enter cookies and localStorage entries that get injected into the verifier's browser

Adding cookies

The browser state editor has two tabs: Cookies and localStorage. Each tab shows a list of key-value pair inputs — one row per entry, with a name/key field and a value field.

To add cookies from your app:

  1. Open your app in Chrome and log in
  2. Open DevTools (F12 or Cmd+Option+I)
  3. Go to Application > Cookies > your domain
  4. Find the relevant cookies (session tokens, auth cookies, etc.)
  5. In the Verify tab's Cookies editor, enter each cookie's name in the first field and its value in the second field

An empty row is always available at the bottom for adding more entries. Values are hidden by default — click the eye icon to reveal them.

Adding localStorage entries

Some apps store auth tokens or user state in localStorage. Switch to the localStorage tab in the editor and add entries the same way:

  1. In Chrome DevTools > Application > Local Storage > your domain
  2. Find the relevant entries (auth tokens, session data, etc.)
  3. Enter each entry's key and value in the editor

Saving

A Save button appears when you've made changes. Click it to store the browser state. Your data is encrypted at rest and scoped to your user account and project.

The tab headers show the count of filled entries (e.g., "Cookies (3)") so you can quickly see what's configured.

Enabling auto-verification

Setting up browser state alone doesn't start verification. You also need to check the Auto-verify after code changes checkbox at the top of the Verify tab.

When enabled, after the agent makes code changes, a separate verification sub-agent will:

  1. Launch a browser
  2. Inject your cookies and localStorage entries
  3. Navigate to your app and check that it works
  4. Take screenshots at each step
  5. Report results back to the coding agent

Verification results and screenshots appear in the Verify tab's run history. The toggle is per-session — you can turn it on for some sessions and off for others.