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.
AI Skills
Use this lesson with the AI assistant you already use
Each agent session got its own Chrome, launched exactly once. When session 11 lost its browser, it was stranded. Finding the cause and shipping the fix took 44 minutes.
Paste the prompt, share only the context needed to answer it, and treat the result as a draft for your review. Do not include confidential information or let an AI assistant make changes without your approval.
Optional: for a visual report and saved memory, run /dxdev first.
Don’t have it? Get it at dxdev.com/skills/dxdev. The prompt works without it.
dxdev LESSON · paste into your AI coding agent
LESSON: Ensure Long-Lived Agent Resources On Use Instead Of Launching Them Once
SOURCE: dxdev.com/blog/2026-07-08_chrome-crash-recovery-agent-sessions
WHAT HAPPENED: The system launched each session's Chrome a single time and never again. If the Chrome crashed, or the author closed the window by hand, the session was left without a browser. Session 11 hit this and was unblocked manually. Finding the cause and shipping the fix took 44 minutes. The fix was a self-heal at the point of use. On the next browser call, the system relaunches the session's Chrome and restores its tabs.
THE RULE: For each long-lived resource in an agent harness, ensure it on use rather than launching it once at startup. A one-time launch means the first crash strands a session and forces manual repair.
CHECK MY CODE, then report PASS or FAIL with file:line for each:
1. List every long-lived resource a session depends on (browser, server, connection) and mark whether it is launched once at startup or verified and re-established when a session asks for it.
2. Kill or close each resource mid-session and confirm the next call that needs it relaunches it and restores its prior state, such as open tabs, without manual intervention.
3. Confirm that closing a window by hand, as a user normally might, does not leave any session permanently without the resource.
THEN PRINT: a table (check, PASS/FAIL, evidence, fix) + a verdict (applies / partially / OUT_OF_SCOPE / no) + the single most important next action.