Skip to content

docs(browser): clarify recovery after a tab or Chrome crash #176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MagMueller merged 3 commits into from
Oct 7, 2026
Merged

docs(browser): clarify recovery after a tab or Chrome crash #176

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d94efb0
fix(browser): surface renderer crashes without losing browser control
MagMueller Oct 7, 2026
6efd96d
refactor(browser): keep crash guidance minimal
MagMueller Oct 7, 2026
42f8a09
docs(browser): limit crash recovery change to one sentence
MagMueller Oct 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions packages/bcode-browser/skills/browser-execute/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,8 @@ await session.use(page.targetId)

If a target-scoped command throws `CdpError` code `-32001` (`Session with given id not found`), the browser connection is still usable but the target session is stale. List targets again, `session.use(...)` the intended page, and retry the rejected command once. Calling `session.connect()` without arguments is a no-op while connected; it does not replace a stale target session.

If a tab or Chrome crashes, recover with a fresh tab or the available browser-replacement API instead of repeatedly retrying the dead page, and verify previous submissions before repeating them.

Every explicit reconnect or browser switch retires the previous socket and clears its active target attachment. Re-list targets, call `session.use(...)`, and rediscover DOM nodes and Runtime objects before continuing.

Opening a tab creates a new `page` target but does not switch the active attachment. Call `Target.getTargets` again and `session.use(targetId)` when continuing there.
Expand Down
Loading