Implements #5168.

It wraps the path in read/write/edit/ls tool titles in an OSC 8 file:// hyperlink when the terminal advertises hyperlink support.

Most of the diff is refactoring: switching to a proper import type { Theme } and a new renderToolPath util that now handles the hyperlink.

Unchanged: grep, find show patterns in their titles, not paths. Their result lines are paths, but that is the same text returned to the model, so I left them as they are.

tmux hyperlink forwarding (pi-tui)

While testing I noticed the links don't work under tmux, so I added a separate commit for packages/tui/src/terminal-image.ts.

This commit is riskier because it executes tmux display-message to read the client's reported features.

I tried to be defensive about it: it runs only under tmux and has a short timeout. If that is not an option we can revert it and instead rely on config or a custom environment variable as a manual workaround.

To see the links under tmux (3.4+), tmux must know the outer terminal supports hyperlinks. It detects this automatically when the terminal's terminfo announces the Hls capability.
For terminals that don't (e.g. Ghostty), it needs to be set manually:

# ~/.tmux.conf
set -as terminal-features '*:hyperlinks'

Extensions

I considered providing an API for extensions, but I droped the idea as custom tools can already support hyperlinks with the existing API fairly easily:

import { resolve } from "node:path";
import { pathToFileURL } from "node:url";
import { getCapabilities, hyperlink, Text } from "@earendil-works/pi-tui";

renderCall(args, theme, context) {
  const styled = theme.fg("accent", args.path);
  const display = getCapabilities().hyperlinks
    ? hyperlink(styled, pathToFileURL(resolve(context.cwd, args.path)).href)
    : styled;
  return new Text(`mytool ${display}`, 0, 0);
}