---
title: Use a Persistent Chrome Profile
description: Point your agent at a Chrome profile directory so login state, cookies, bookmarks, and extensions persist between sessions.
---

# Use a Persistent Chrome Profile

<div class="view-markdown-wrapper">
<ViewMarkdown />
</div>

Instead of starting fresh every time, you can point your agent at a Chrome profile directory. Everything persists between sessions — login state, cookies, bookmarks, extensions, localStorage.

**First time — create a profile and log in:**

```
/shiplight verify https://app.example.com — use the Chrome profile
at ./my-chrome-profile. I'll log in manually.
```

Log in once in the browser window. The profile saves everything.

**Subsequent sessions — your login is already there:**

```
/shiplight verify https://app.example.com/dashboard —
use the Chrome profile at ./my-chrome-profile
```

No credentials, no storage state files, no setup — just point to the profile directory and go. This works great for:

- **Apps with Google OAuth / SSO** — log in once manually, reuse forever
- **Complex authenticated state** — multi-step onboarding, 2FA, org switching
- **Extension testing** — combine with `path_to_extension` to test extensions with real login state

Without a Chrome profile, a fresh temp profile is created and cleaned up when the session closes.