Feature Request: Support clickable file paths in SSH sessions to open remote files

[murphy2333]

Description

When using VS Code's integrated terminal with Remote SSH, clicking on a filename
in command output (e.g., ls) automatically opens that file in the editor.
This is an extremely productive workflow that Windows Terminal currently cannot replicate.

Problem

Windows Terminal already supports OSC 8 hyperlinks and basic URL detection.
However, when connected to a remote host via SSH, there is no mechanism to:

1. Recognize filenames in command output (e.g., from ls, find, grep) as clickable targets
2. Communicate back to the remote shell to perform an action (e.g., open the file in an editor)

The fundamental gap is that OSC 8 link clicks are handled entirely on the Windows side,
with no way to trigger an action on the remote shell side.

Proposed Solution

Introduce a configurable "terminal action protocol" that allows click events on
recognized patterns to be sent back to the running shell session as commands. For example:

• User Ctrl+Clicks a filename in ls output
• Windows Terminal detects it as a file path pattern
• Terminal sends a configurable command (e.g., $EDITOR <filepath>) as input to the active shell session

This could be implemented as:

1. A new escape sequence (e.g., extended OSC) that lets the remote shell register
   "clickable regions" with associated shell commands, not just URIs
2. A built-in pattern matcher (configurable in settings.json) that maps recognized
   file paths to shell input actions
3. Shell integration protocol similar to what iTerm2/WezTerm offer, where the shell
   can advertise its capabilities and the terminal can send actions back

Comparison

Terminal	SSH file click support
VS Code Terminal + Remote SSH	Full support (opens in editor)
iTerm2	Semantic history + shell integration
WezTerm	Configurable hyperlink rules + actions
Windows Terminal	Not supported

Use Case

user@remote:~$ ls
main.py config.yaml README.md
^^^^^^^^
Ctrl+Click → opens in $EDITOR on the remote host

This would make Windows Terminal significantly more competitive with VS Code's
integrated terminal for remote development workflows.

Environment

• Windows Terminal (latest)
• SSH to remote Linux hosts
• Common shells: bash, zsh