›_ Claude Code Issues
Claude Code Issues / #71658

[Bug] OSC 8 hyperlinks to local HTML files open Finder instead of web browser

Open 💬 0 comments Opened Jun 26, 2026 by mdwhatcott

Bug Description

Full-screen rendering: clickable file:// HTML links open Finder instead of the browser

Summary

With full-screen rendering enabled, file paths to local .html files are emitted
as OSC 8 hyperlinks. In Ghostty on macOS, cmd+clicking these links opens Finder
instead of the default browser. Before full-screen rendering, the same paths
were printed as plain-text file:///… URLs, which Ghostty auto-linkified and passed
to macOS open, correctly launching the browser for .html files.

Environment

  • Claude Code with "Full Screen Rendering" enabled
  • Terminal: Ghostty 1.3.1
  • macOS Tahoe 26.5.1

Steps to reproduce

  1. Enable full-screen rendering.
  2. Have Claude Code emit a link to a local HTML file (e.g. a generated

doc/work-sessions/<date>-proposal-<desc>.html), shown as a clickable
OSC 8 hyperlink.

  1. cmd+click the link in Ghostty.

Expected

The .html file opens in the default web browser (the prior behavior with
plain-text file:// URLs).

Actual

A Finder window opens at the file's location instead of the browser.

Analysis

  • Web-scheme links (http(s)://) cmd+clicked in Ghostty route by URL scheme to the

default browser. file:// links and bare paths are treated as files and routed
through macOS file handling, which results in a Finder reveal rather than opening
the file's default-handler app (the browser).

  • The regression is specific to how full-screen rendering encodes the link

(OSC 8 hyperlink with a file:///path target) versus the older plain-text
file:// URL.

Requested fix

When rendering links to local files, either:

  • keep the bare-text file:// form so Ghostty/macOS open launches the default

handler (browser for .html), or

  • open local links via the default application for the file type rather than

performing a Finder reveal.

Impact

This affects every repository where these HTML-generating workflows are used (in my
case, several dozen). The only reliable workaround is running a local static HTTP
server and rewriting links to http://localhost, which is cumbersome across many
repos.

Environment Info

  • Platform: darwin
  • Terminal: ghostty
  • Version: 2.1.193
  • Feedback ID: b67fa912-0075-496e-8d12-a7ee8b7333a8

Errors

[]

View original on GitHub ↗