---
title: "The one-time Chrome launch that stranded session 11 without a browser"
canonical: https://dxdev.com/blog/chrome-crash-recovery-agent-sessions/
datePublished: 2026-07-08
---
Session 11 had no browser, and it was not the first session to lose one.

## One launch, no second chance

Each agent session gets its own Chrome. The system launched that Chrome once and never again. That holds until the Chrome crashes, or until someone closes the window by hand. After either, the session is stranded without a browser.

## Unblocking session 11 by hand

I unblocked session 11 by hand and got it running again. Finding the cause and shipping the fix took 44 minutes in all.

## Ensure on use, not launch once

The fix is a self-heal. On the next browser call, the system relaunches the session's Chrome and restores its tabs. The session makes a browser call and gets a browser, with its tabs back where they were.

The repair now happens at the point of use. Launching used to be a one-time event. Now it is something the system re-establishes whenever a session asks for a browser.

For each long-lived resource in an agent setup, there is a question worth asking: is it launched once, or ensured on use? If it is launched once, the first crash strands a session, and someone has to unblock it by hand. So check whether each session's resources are re-established when the session asks for them.