One of the most common requests we’ve heard:

**“Can Skyvern pick up where it left off?”**

Until now, every run started fresh—like opening a brand new browser window each time. Clean, but sometimes too clean.

## Why Browser Sessions?

Skyvern **Browser Sessions** prop up a browser and let you persist the real-time state of the browser

This unlocks a whole new category of workflows where context matters:

- **Deploy code straight into the browser —** combine AI navigations and trusty ‘ol code by CDPing into our browser sessions before / after the AI tasks are done  
- **Continuous tasks with no lag —** connect the browser across multiple workflows so you can use Skyvern for real-time executions

* * *

## How it works

1. **Create a browser session** via API or SDK  
2. **Run tasks inside that session** — they’ll share state, cookies, and progress  
3. **Resume at any time** — reconnect to the session and keep going from where you stopped

📘 [See the docs →](https://docs.skyvern.com/api-reference/api-reference/browser-sessions/create-browser-session?ref=skyvern.com)

* * *

🔥 Real-time persistence. Continuous agents. Smarter workflows. We’re hoping Browser Sessions give you flexibility to run, rerun, deploy code, and stay logged in without starting over.