You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Open local HTML previews in Chrome on macOS #57708
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
On macOS Desktop v2.0.32, the workspace “Open in” menu lists Finder and supported editors, but not Chrome. The HTML viewer's existing browser action opens the built-in browser, not Chrome.
Could we add “Open in Chrome” to the current HTML file's preview toolbar?
Proposed scope:
macOS Desktop, local sessions, HTML files only.
Show the action only when Google Chrome is detected.
Open the current file's resolved absolute path using the existing desktop launcher.
Preserve the built-in preview, editor preferences, and system default browser.
Prevent duplicate launches and report launch failures.
Related: #57477 and #55858; this would not fully resolve either.
I'd like design approval before implementing, as requested by CONTRIBUTING.md. The implementation would include regression tests and before/after UI evidence.
Thanks for the detailed proposal, @xianshang33! You're asking for an Open in Chrome action in the HTML file preview toolbar on macOS Desktop. It would show only when Chrome is installed and open the file's absolute path with the existing desktop launcher, leaving the built-in preview and the default browser as they are.
Maintainers will consider it and decide on the design. Related issues:
Activity
opencode-agent commentedon Oct 21, 2026
Thanks for the detailed proposal, @xianshang33! You're asking for an Open in Chrome action in the HTML file preview toolbar on macOS Desktop. It would show only when Chrome is installed and open the file's absolute path with the existing desktop launcher, leaving the built-in preview and the default browser as they are.
Maintainers will consider it and decide on the design. Related issues:
Plugins can't add buttons to the Desktop UI right now, so this can't be done as a plugin in the meantime.