Windows: embedded browser can't be closed after clicking link in response

[Pililink]

Description

On Windows 11, clicking a link in an assistant response opens the built-in browser, but it cannot be closed. 100% reproducible.

Plugins

oh-my-opencode

OpenCode version

1.1.36

Steps to reproduce

1. Open OpenCode Desktop (v1.1.36) on Windows 11.
2. Ask a prompt that returns a link in the response.
3. Click the link in the response.
4. The built-in browser opens.

Screenshot and/or share link

https://opncd.ai/share/JAtIY0B2

Operating System

windows11

Terminal

No response

[github-actions]

This issue might be a duplicate of or related to existing issues about link handling in the desktop app. Please check:

• URL opening within opencode desktop app #10110: URL opening within opencode desktop app (similar issue on macOS)
• when click on a link ,in opencode desktop , it opens the link in the same window , not external browser #8361: When click on a link in opencode desktop, it opens the link in the same window, not external browser
• Desktop: Option to open links in external browser #10309: Desktop: Option to open links in external browser (feature request for external browser option)
• Opening a link within the Linux app brings you to a "dead end" #6484: Opening a link within the Linux app brings you to a "dead end" (similar issue on Linux - no way to escape)

These issues are related to how the embedded browser handles link clicks. The core difference with #10613 is that on Windows, the browser opens but cannot be closed, whereas other platforms have the browser opening in-app or providing limited navigation options.