---
title: "The Self-Healing Browser: Recovering Agent Sessions From Crashes"
canonical: https://dxdev.com/blog/2026-07-08_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 I close the window myself. After either, the session is stranded without a browser.

## The manual unblock

For session 11 I unblocked it by hand and got it running again. The whole task, finding the cause and shipping the fix, took 44 minutes.

## 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 happens at the point of use. Launching used to be a one-time event, and now it is something the system re-establishes whenever a session asks for a browser.

For any agent harness, the question to ask of each long-lived resource is whether it is launched once or ensured on use. If it is launched once, the first crash strands a session, and you end up doing the unblocking by hand.