Skip to content

feat(desktop): add on-demand browser pane - #39278

Closed
Hona wants to merge 2 commits into
browser-chromium-driverfrom
browser-app-ui
Closed

feat(desktop): add on-demand browser pane#39278
Hona wants to merge 2 commits into
browser-chromium-driverfrom
browser-app-ui

Conversation

@Hona

@HonaHona commented Jul 28, 2026

Copy link
Copy Markdown
Member

What does this PR do?

Adds the complete Desktop/App consumer:

  • lightweight Session registration while the pane is closed
  • browser_open event reveals the owning Session pane
  • Chromium attaches only while the pane is visible
  • isolated Electron WebContentsView and proxy-only networking
  • typed IPC, origin policy, bounds, and destroyed-window cleanup
  • minimal App native surface integration

There 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

  • Tested locally
  • No unrelated changes

@HonaHona changed the title feat(app): add browser pane UIfeat(desktop): add on-demand browser paneJul 29, 2026
@Hona
Hona changed the base branch from desktop-browser to browser-chromium-driverJuly 29, 2026 06:06
@Hona

Hona commented Jul 29, 2026

Copy link
Copy Markdown
MemberAuthor

End-to-end verification on the simplified stack:

  • authenticated OpenAI ChatGPT subscription on the isolated VPS
  • GPT-5.5 low received only browser_open while detached
  • browser_open visibly mounted the Desktop Chromium pane
  • the next model step received browser_navigate and browser_snapshot
  • Desktop navigated through the authenticated local proxy and simplified remote tunnel to http://127.0.0.1:18080 on the VPS
  • semantic snapshot returned heading VPS tunnel reached honacloud loopback

No Chromium CDP target existed before browser_open; one appeared after attachment.

@Hona

Hona commented Aug 25, 2026

Copy link
Copy Markdown
MemberAuthor

Consolidated into #39270, which now contains the complete experimental browser feature and targets v2 directly.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@Hona