What happens
Claude Code prints file paths constantly — plan files, source locations, diffs. In Warp there is no way to click one and land in an editor. I tested every route:
| link form |
result |
cursor://file/path as OSC 8 |
rejected by the scheme allowlist, renders as literal text |
file:///path as OSC 8 |
clickable, but reveals in Finder |
bare /abs/path |
inert — Warp's path linkifier doesn't run over an alternate-screen TUI |
Claude Code's footerLinksRegexes |
generates the link correctly, then inherits all of the above |
Settings → Features → General → Choose an editor to open file links is set to Cursor and has no effect on any of these.
Why file:// is the interesting one
warpdotdev/warp#4194, the OSC 8 implementation issue, poses this exact question — which schemes are permitted, and whether file:// should open an editor or Finder. Finder was chosen and the choice was never exposed.
Notably, Warp isn't following the system here either. /usr/bin/open "file:///Users/me/notes.md" brings my configured editor to the front; clicking the identical URL in Warp opens Finder. So Warp is overriding LaunchServices, not deferring to it.
The ask
Route OSC 8 file:// links through the existing [code.editor] open_file_editor setting, the same way command-output file paths already are.
This needs no allowlist changes and no new configuration — the setting exists and is already populated. It's one code path reading a preference it currently ignores.
Why it matters here specifically
This is the integration repo for a tool whose entire output is file paths. Every path Claude Code prints is currently a dead end in Warp, while it's clickable in Ghostty, iTerm2, and VS Code's terminal.
A fallback would be honouring LaunchServices for file:// instead of forcing Finder — that alone would fix it, since users already map file types to their editor at the OS level.
Environment
macOS 15.5, Warp (latest), Claude Code 2.1.x.
What happens
Claude Code prints file paths constantly — plan files, source locations, diffs. In Warp there is no way to click one and land in an editor. I tested every route:
cursor://file/pathas OSC 8file:///pathas OSC 8/abs/pathfooterLinksRegexesSettings → Features → General → Choose an editor to open file linksis set to Cursor and has no effect on any of these.Why
file://is the interesting onewarpdotdev/warp#4194, the OSC 8 implementation issue, poses this exact question — which schemes are permitted, and whether
file://should open an editor or Finder. Finder was chosen and the choice was never exposed.Notably, Warp isn't following the system here either.
/usr/bin/open "file:///Users/me/notes.md"brings my configured editor to the front; clicking the identical URL in Warp opens Finder. So Warp is overriding LaunchServices, not deferring to it.The ask
Route OSC 8
file://links through the existing[code.editor] open_file_editorsetting, the same way command-output file paths already are.This needs no allowlist changes and no new configuration — the setting exists and is already populated. It's one code path reading a preference it currently ignores.
Why it matters here specifically
This is the integration repo for a tool whose entire output is file paths. Every path Claude Code prints is currently a dead end in Warp, while it's clickable in Ghostty, iTerm2, and VS Code's terminal.
A fallback would be honouring LaunchServices for
file://instead of forcing Finder — that alone would fix it, since users already map file types to their editor at the OS level.Environment
macOS 15.5, Warp (latest), Claude Code 2.1.x.