Uh oh!
There was an error while loading. Please reload this page.
feat(desktop): add on-demand browser pane - #39278
Closed
Hona wants to merge 2 commits into
Closed
Conversation
2 tasks
Hona
commented
Jul 29, 2026
MemberAuthor
End-to-end verification on the simplified stack:
No Chromium CDP target existed before |
6 tasks
Hona
commented
Aug 25, 2026
MemberAuthor
Consolidated into #39270, which now contains the complete experimental browser feature and targets v2 directly. |
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Adds the complete Desktop/App consumer:
browser_openevent reveals the owning Session paneThere is no hidden Chromium, persisted browser layout, experimental setting, manual toggle, browser toolbar, cross-window ownership protocol, retained context, or crash reattachment loop.
Verification
Desktop and App typechecks pass. All 69 Desktop tests pass, including the observed destroyed-window cleanup regression. Production Desktop build succeeds. The real Desktop registers a remote Session without creating a Chromium target.
Checklist