Add warning about browser.close() affecting profile saving #195
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a warning that calling browser.close() before deleting kernel browsers will shut down Chromium and cause profile saving to fail. Changed the callout type from Info to Warning to better reflect the severity of this issue.
Files changed:
Created by Mintlify agent
Note
Low Risk
Documentation-only change that adjusts guidance/warnings around browser termination; no runtime behavior is modified.
Overview
Clarifies profile persistence docs to prevent accidental loss of saved state when using
save_changes: true.Updates
browsers/profiles.mdxto warn thatbrowser.close()both does not persist profile state and can shut down Chromium before the Kernel browser is deleted, causing profile saving to fail; reinforces deleting the Kernel browser (or letting it timeout) as the required persistence mechanism.Written by Cursor Bugbot for commit 21bbbe1. This will update automatically on new commits. Configure here.