Desktop: make file paths in chat clickable (open in editor / reveal in Finder)

[tauseefkhan-max]

Summary

In the OpenCode desktop app, file and folder paths rendered in assistant messages look like interactive chips/links, but they are not clickable. Markdown file:// links are also not clickable. There is no way to open a referenced path in the built-in editor, system default app, or Finder/Explorer from the chat transcript.

Environment

• OpenCode Desktop (macOS)
• Model: Grok 4.5 (via OpenCode)
• Observed: 2026-07-20

Steps to reproduce

1. Ask the agent to list files in a folder (or any reply that includes absolute paths).
2. Paths render as styled chips (gray background), e.g. `/Users/.../file.md`.
3. Click a chip → nothing happens.
4. Ask the agent to emit markdown links instead:

   [file.md](file:///Users/me/project/file.md)

5. Click the link → nothing happens (links are not interactive).

Expected

Clicking a path/link in chat should offer a useful action, for example:

• Primary click: open file in OpenCode’s built-in editor / file browser tab
• Secondary / modifier: Reveal in Finder (macOS) / Explorer (Windows) / file manager (Linux)
• Folders: open in file browser or reveal in Finder
• Optional: path:line / path:line:col jumps to location

Actual

Paths and file:// markdown links are non-interactive. Users must copy the path and run something like:

open -R "/full/path/to/file"

or ask the agent to run open for them.

Why this matters

Agents constantly point at files they created or edited. Click-to-open is table stakes in Cursor/VS Code/Claude Code-style UIs and removes a constant copy-paste friction, especially for non-code artifacts (PDFs, PNGs, .docx, data folders).

Related

• [FEATURE]: open files in built-in editor in web ui #31406 — open files in built-in editor in web UI
• [FEATURE]: Built-in File Explorer Panel #36512 — built-in file explorer panel
• [FEATURE]:Enhanced file management #30074 — enhanced file management
• PR feat(web): file mentions now open files in the editor #31407 — file mentions open in editor (closed/abandoned)
• PR feat(tui): make file tool titles clickable #30404 — make file tool titles clickable (closed/abandoned)
• PR feat(app): add inline file browser tabs #35829 — inline file browser tabs (merged) — suggests UI surface already exists to open into

Suggested acceptance criteria

1. Absolute and workspace-relative paths in assistant markdown become clickable.
2. Click opens the file in the desktop file browser/editor when possible.
3. Right-click or modifier-click reveals the path in the OS file manager.
4. Invalid/missing paths show a clear toast instead of silently doing nothing.
5. Works for both inline code paths and markdown links (file:// and relative).

Thanks — happy to test a nightly/desktop build.

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• [FEATURE]: Make local file paths clickable in terminal output #19005: Make local file paths clickable in terminal output — same core request (clickable file paths, file:// protocol, avoiding manual copy-paste)
• [FEATURE]:[Web]: Clickable file:line references in messages (jump to file and line) #13430: Clickable file:line references in messages (jump to file and line) in web UI — very similar request for clickable file references in chat messages

Please review these issues before continuing, and consider adding your input there instead of opening a new issue.